9Router through version 0.4.41 contain 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.
CVE-2026-62327
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.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(high)
- EPSS
- —
- KEV
- Not listed
Published
July 13, 2026
Last Modified
July 13, 2026
Advisory Details (2)
Auto-updated Jul 13, 20269Router 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-statsUnauthenticated 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-9j86Vendor 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.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× 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.
- 2026-07-14 06:21 UTCEG score recompute
- 2026-07-14 06:21 UTCGHSA enrichment
- 2026-07-14 02:02 UTCEG score recompute
- 2026-07-14 02:02 UTCGHSA enrichment
- 2026-07-13 21:43 UTCEG score recompute
- 2026-07-13 21:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306 · CWE-522
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS 97%CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2013-7055EG 9.8EPSS 93%CRITICAL
- CVE-2013-7052EG 9.8EPSS 98%CRITICAL
- CVE-2014-3445EG 9.8EPSS 92%CRITICAL
- CVE-2014-5381EG 9.8EPSS 93%CRITICAL
- CVE-2014-5093EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-62327?
When was CVE-2026-62327 disclosed?
What is the CVSS score of CVE-2026-62327?
How do I remediate CVE-2026-62327?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62327
Is Your Infrastructure Affected by CVE-2026-62327?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.