CVE-2026-49352

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 55% 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
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: 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. From 0.2.21 until 0.4.44, 9Router used the hardcoded fallback JWT secret 9router-default-secret-change-me in src/app/api/auth/login/route.js, src/middleware.js, and later src/lib/auth/dashboardSession.js, allowing attackers to forge an auth_token cookie when JWT_SECRET was unset. This issue is fixed in version 0.4.44

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
EPSS
45.1%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 16, 2026

Advisory Details (3)

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

Hardcoded Default fallback JWT Secret Allows Authentication Bypass · Advisory · decolua/9router · GitHub

https://github.com/decolua/9router/security/advisories/GHSA-jphh-m39h-6gwx
github_release Patch Available

feat: Add Blackbox & Xiaomi providers, model select UX version 0.4.44

Patch available: decolua/9router v0.4.44

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

commit fe3ce25ae3cd (decolua/9router)

Patch available: decolua/9router v0.4.44 (contains commit fe3ce25ae3cd)

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

Vendor Advisories for CVE-2026-49352(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
9router0.4.45

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 9× 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-02 21:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49352?
CVE-2026-49352 is a critical vulnerability published on July 2, 2026. 9Router is an AI router & token saver. From 0.2.21 until 0.4.44, 9Router used the hardcoded fallback JWT secret 9router-default-secret-change-me in src/app/api/auth/login/route.js, src/middleware.js, and later src/lib/auth/dashboardSession.js, allowing attackers to forge an authtoken cookie when…
When was CVE-2026-49352 disclosed?
CVE-2026-49352 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49352 actively exploited?
CVE-2026-49352 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 45.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49352?
CVE-2026-49352 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-49352?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49352, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49352

Explore →

Is Your Infrastructure Affected by CVE-2026-49352?

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