dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-56678

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
9Router is an AI router & token saver. Prior to 0.5.6, the Kiro API-key validation endpoint POST /api/oauth/kiro/api-key builds an upstream URL using a user-controlled region value, allowing an authenticated attacker to supply a crafted region such as kiro-canary.local:8443# and cause 9Router to send the Kiro validation request to an attacker-controlled host while forwarding the submitted Kiro API key as an Authorization header. This issue is fixed in version 0.5.6.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Kiro API-key validation endpoint POST /api/oauth/kiro/api-key constructs an upstream URL using a user-controlled region parameter without proper validation. An authenticated attacker can supply a crafted region value (e.g., kiro-canary.local:8443#) to redirect the validation request to an attacker-controlled server while forwarding the submitted Kiro API key as an Authorization header, resulting in SSRF with credential theft.

MitigationUpgrade to version 0.5.6 or later. As a compensating control, implement strict allowlist validation for the region parameter to only permit legitimate region values.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Kiro API is deployed
    Search for Kiro API service files, Docker containers, or running processes named 'kiro'. Check for any /api/oauth/kiro/api-key endpoint exposure in your API gateway or reverse proxy logs.
    Affected if Kiro API service is found running in the environment
  2. Determine installed Kiro version
    Check the Kiro service version via its binary (kiro --version), Docker image tag, or package manager. Compare against the fixed version 0.5.6.
    Affected if Installed version is lower than 0.5.6 or version cannot be determined
  3. Verify the vulnerable endpoint exists
    Confirm POST /api/oauth/kiro/api-key is accessible by checking your API routing configuration, OpenAPI specs, or by sending a test request to the endpoint (may require authentication).
    Affected if The /api/oauth/kiro/api-key endpoint is exposed and reachable
  4. Inspect region parameter validation
    Review the Kiro API source code or configuration for how the 'region' parameter in the /api/oauth/kiro/api-key endpoint is validated. Look for allowlist logic that restricts region values.
    Affected if No strict allowlist validation exists for the region parameter, or validation can be bypassed
  5. Check for suspicious outbound requests
    Review network logs, proxy logs, or API gateway logs for requests from the Kiro API server to unusual external hosts, particularly on ports 8443 or 443, with paths containing 'kiro-' or suspicious domains.
    Affected if Outbound requests from Kiro API are observed to unknown external domains, especially with the API key in Authorization headers

The environment is affected if Kiro API with version lower than 0.5.6 is deployed and the /api/oauth/kiro/api-key endpoint is accessible without strict region parameter allowlist validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 0.5.6 or later. As a compensating control, implement strict allowlist validation for the region parameter to only permit legitimate region values.

Recommended fix High confidence

0.5.6

  1. Upgrade 9Router to version 0.5.6 or later to remediate the improper input validation vulnerability in the Kiro API-key validation endpoint
  2. After upgrading, verify that the Kiro API-key validation functionality still works correctly
  3. Review any custom configurations related to the region parameter to ensure compatibility with the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56678 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56678 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data