CVE-2026-56675

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
—
EPSS
23.8%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (3)

Auto-updated Jul 10, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github Patch Available🟡 PoC Available

Reverse proxy locality collapse allows unauthenticated access to 9router /v1 APIs · Advisory · decolua/9router · GitHub

https://github.com/decolua/9router/security/advisories/GHSA-x5c9-v98j-722r
github_release Patch Available

feat: Combo Fusion + Capacity auto-switch, Kiro API-key, Claude auto-ping & 429 throttle version 0.5.2

Patch available: decolua/9router v0.5.2

https://github.com/decolua/9router/releases/tag/v0.5.2
github_commit Patch Available

commit da667836cc75 (decolua/9router)

Patch available: decolua/9router v0.5.2 (contains commit da667836cc75)

https://github.com/decolua/9router/commit/da667836cc7584bea0edd893de1d590c9ea279dc

Weakness Classification(4)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 22:31 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-10 16:33 UTCEG score recompute
  18. 2026-07-10 16:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56675?
CVE-2026-56675 is a high vulnerability published on July 10, 2026. 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…
When was CVE-2026-56675 disclosed?
CVE-2026-56675 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56675 actively exploited?
CVE-2026-56675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56675?
CVE-2026-56675 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-56675?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56675, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56675

Explore →

Is Your Infrastructure Affected by CVE-2026-56675?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs