CVE-2026-62327

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-14. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

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

9Router through version 0.4.41 contains an unauthenticated information disclosure vulnerability that allows remote attackers to retrieve plaintext API keys for all connected AI provider accounts by sending a single unauthenticated request to the /api/usage/stats endpoint. Attackers can exploit the missing authentication middleware on the Next.js API route to obtain full API key strings alongside token counts, cost breakdowns, and request metadata, enabling unauthorized use of connected AI provider accounts, billing fraud, and quota exhaustion.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 13, 2026
Patch available. Sources: github.
generic

9Router 0.4.41 - Unauthenticated API Key Exposure via /api/usage/stats | Advisories | VulnCheck

https://www.vulncheck.com/advisories/9router-unauthenticated-api-key-exposure-via-api-usage-stats
github Patch Available

Unauthenticated CRUD on /api/providers and Full API Key Leak via /api/usage/stats · Advisory · decolua/9router · GitHub

https://github.com/decolua/9router/security/advisories/GHSA-vjc7-jrh9-9j86

Vendor Advisories for CVE-2026-62327(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
9router———

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 50× 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-27 14:14 UTCEPSS rescore
  2. 2026-07-27 09:25 UTCGHSA enrichment
  3. 2026-07-27 05:07 UTCGHSA enrichment
  4. 2026-07-27 00:48 UTCGHSA enrichment
  5. 2026-07-26 20:28 UTCGHSA enrichment
  6. 2026-07-26 16:10 UTCEG score recompute
  7. 2026-07-26 16:10 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 11:51 UTCEG score recompute
  11. 2026-07-26 11:51 UTCGHSA enrichment
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-25 14:18 UTCEPSS rescore
  14. 2026-07-24 14:18 UTCEPSS rescore
  15. 2026-07-24 14:18 UTCEPSS rescore
  16. 2026-07-23 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 03:22 UTCEG score recompute
  19. 2026-07-22 14:08 UTCEPSS rescore
  20. 2026-07-22 14:08 UTCEPSS rescore
  21. 2026-07-21 15:25 UTCEPSS rescore
  22. 2026-07-21 15:25 UTCEPSS rescore
  23. 2026-07-20 17:08 UTCEPSS rescore
  24. 2026-07-19 14:31 UTCEPSS rescore
  25. 2026-07-19 02:29 UTCEPSS rescore
Show 25 more
  1. 2026-07-18 10:04 UTCEPSS rescore
  2. 2026-07-17 03:07 UTCGHSA enrichment
  3. 2026-07-16 22:50 UTCGHSA enrichment
  4. 2026-07-16 18:32 UTCGHSA enrichment
  5. 2026-07-16 17:03 UTCEPSS rescore
  6. 2026-07-16 14:14 UTCGHSA enrichment
  7. 2026-07-16 09:57 UTCGHSA enrichment
  8. 2026-07-16 05:40 UTCGHSA enrichment
  9. 2026-07-16 01:22 UTCGHSA enrichment
  10. 2026-07-15 21:04 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 16:46 UTCGHSA enrichment
  13. 2026-07-15 12:26 UTCGHSA enrichment
  14. 2026-07-15 08:09 UTCGHSA enrichment
  15. 2026-07-15 03:50 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 23:33 UTCGHSA enrichment
  19. 2026-07-14 19:14 UTCGHSA enrichment
  20. 2026-07-14 14:57 UTCGHSA enrichment
  21. 2026-07-14 10:39 UTCGHSA enrichment
  22. 2026-07-14 06:21 UTCGHSA enrichment
  23. 2026-07-14 02:02 UTCGHSA enrichment
  24. 2026-07-13 21:43 UTCEG score recompute
  25. 2026-07-13 21:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62327?
CVE-2026-62327 is a critical vulnerability published on July 13, 2026. 9Router through version 0.4.41 contains an unauthenticated information disclosure vulnerability that allows remote attackers to retrieve plaintext API keys for all connected AI provider accounts by sending a single unauthenticated request to the /api/usage/stats endpoint. Attackers can exploit the…
When was CVE-2026-62327 disclosed?
CVE-2026-62327 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62327 actively exploited?
CVE-2026-62327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.3% of all scored CVEs.
What is the CVSS score of CVE-2026-62327?
CVE-2026-62327 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-62327?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62327, 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-62327

Explore →

Is Your Infrastructure Affected by CVE-2026-62327?

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

Start Free Scan →Browse All CVEs