Skip to main content
VulnerabilityPublished Updated

CVE-2026-56681: decolua 9router · Reliance on Untrusted Inputs in a Security Decision

Affects decolua 9routerSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 7.3 High : upgrade to 0.5.6 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.5.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade 9router and decolua/9router to 0.5.6.

Affected software

ProductAffectedFixed in
decolua9routerAffected
  • <0.5.6
Fixed in
  • 0.5.6
GitHubdecolua/9routerpkg:github/decolua/9routerOther threatsAffected
  • <0.5.6
Fixed in
  • 0.5.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to version 0.5.6 or later where this issue is fixed. Prior to upgrading, ensure that requests to Next.js are properly sanitized and that the X-9r-Real-Ip header is not trusted for security decisions. No other vendor advisory information is provided, so patching to 0.5.6 is the recommended remediation.

Description

9Router is an AI router & token saver. Prior to 0.5.6, 9Router deployments that allow requests to reach Next.js without the sanitizing custom-server.js wrapper trust the client-supplied X-9r-Real-Ip header in src/dashboardGuard.js when isLocalRequest decides whether canAccessPublicLlmApi may skip API-key validation for /api/v1/* routes. A remote unauthenticated attacker can set X-9r-Real-Ip to 127.0.0.1 and be classified as a local client, including on the verified GET /api/v1/models route. This permits unauthorized use of the instance owner's configured LLM providers, consumption of paid credits, and enumeration of configured providers and models. This issue is fixed in version 0.5.6.

References

Community reviews

Loading reviews…