dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-56675

HIGH · 8.3 CVSS v3.1 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 6 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.2, 9router treats loopback requests as trusted and allows /v1/* access without an API key, so a same-host reverse proxy that forwards public traffic to the backend through 127.0.0.1 causes src/dashboardGuard.js to misclassify external requests as local. A remote unauthenticated attacker can access /v1 APIs such as /v1/models and may abuse configured upstream provider credentials through /v1 proxy endpoints depending on enabled providers. This issue is fixed in version 0.5.2.

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 · moderate confidence

9Router versions prior to 0.5.2 have an authentication bypass in src/dashboardGuard.js where requests originating from the loopback interface (127.0.0.1) are implicitly trusted and granted access to /v1/* endpoints without API key validation. An attacker can exploit this by routing external traffic through a same-host reverse proxy to the backend via localhost, causing the code to misclassify remote requests as local and bypass authentication. This allows unauthenticated access to sensitive /v1 APIs including /v1/models and potential abuse of configured upstream provider credentials.

MitigationUpgrade to version 0.5.2 which contains the fix for this trust boundary confusion. As a temporary measure, ensure no reverse proxy forwards external traffic to 127.0.0.1 without additional authentication.

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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Determine installed 9Router version
    Run '9router --version' or check package.json if running from source, or check the binary/container version metadata
    Affected if Version is below 0.5.2
  2. Verify dashboardGuard.js is present
    Locate the src/dashboardGuard.js file in the 9Router installation directory or source code repository
    Affected if The file exists and contains logic that trusts 127.0.0.1 requests without API key validation
  3. Confirm /v1 API endpoints are enabled
    Review the server configuration or application startup logs to verify that /v1/* endpoints are actively routed
    Affected if The /v1 API endpoints are enabled and accessible
  4. Check for reverse proxy configuration
    Inspect any reverse proxy (nginx, Apache, traefik, or custom) configuration files that may forward traffic to 127.0.0.1
    Affected if A reverse proxy is configured to forward external requests to the localhost-bound backend service
  5. Verify network binding configuration
    Check which interfaces and IP addresses the 9Router service is bound to (check config files or running process with 'netstat' or 'ss')
    Affected if The service binds to 127.0.0.1 and is reachable via localhost without additional authentication

You are affected if 9Router version is below 0.5.2 AND the /v1 API endpoints are accessible through a reverse proxy that forwards traffic to localhost, allowing the trust boundary confusion to be exploited.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.5.2 which contains the fix for this trust boundary confusion. As a temporary measure, ensure no reverse proxy forwards external traffic to 127.0.0.1 without additional authentication.

Recommended fix High confidence

0.5.2

  1. Check the currently installed version of 9router by running 'npm list 9router' or checking package.json
  2. Upgrade to version 0.5.2 using 'npm install [email protected]' or 'npm update 9router'
  3. If using a package manager like yarn, run 'yarn install [email protected]'
  4. Restart the 9router service after upgrading
  5. Verify the version upgrade was successful by checking 'npm list 9router'

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56675 — 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-56675 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