CVE-2026-56675: decolua 9Router authentication bypass via loopback trust collapse

CVE-2026-56675 · Severity: high · CVSS 8.3 · Published 2026-07-10

9Router, an AI routing and token management tool, contains a security flaw that allows unauthorized users to bypass authentication when the software is used behind a standard reverse proxy like Nginx. Because the router incorrectly trusts all traffic coming from the local proxy as 'safe,' an attacker can access the system's AI models and APIs without a valid key. This could allow unauthorized parties to use the owner's paid AI service credentials, leading to unexpected costs and data exposure.

Technologies: 9router (npm). Vendors: npm.

Quick answers

Is CVE-2026-56675 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-56675 being exploited in the wild.
How severe is CVE-2026-56675?
High severity, with a CVSS score of 8.3, published 10 July 2026.
Which products and versions are affected?
9router (npm) <= 0.4.80, SEMVER:introduced=0,fixed=0.5.2.
Is there a fix for CVE-2026-56675?
Yes. 9router (npm): upgrade to 0.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56675 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-56675?
Check whether you run 9router (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • 9router (npm): upgrade to 0.5.2 or later
    npm install 9router@0.5.2

Technical details

9Router (prior to version 0.5.2) contains an authentication bypass vulnerability in its 'dashboardGuard.js' component. The application incorrectly assumes that any request originating from the loopback address (127.0.0.1) is a trusted local request and does not require an API key for /v1/* endpoints. When deployed behind a reverse proxy (such as Nginx) on the same host, all external traffic is forwarded via the loopback interface, causing the application to misclassify remote requests as local. An unauthenticated remote attacker can exploit this to access sensitive endpoints like /v1/models and /v1/chat/completions, potentially exhausting the operator's upstream AI provider quotas. The fix, introduced in v0.5.2, involves checking for forwarding headers (X-Forwarded-For/X-Real-IP) to ensure proxy hops are not treated as trusted local users.

Affected products

  • decolua 9router < 0.5.2

Identifiers

  • CVE-2026-56675
  • GHSA-x5c9-v98j-722r

Timeline

  • 2026-06-17: patched: Version 0.5.2 released
  • 2026-07-07: advisory: GitHub Security Advisory published
  • 2026-07-10: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.