CVE-2026-62327
Unauthenticated API leak exposes plaintext AI provider API keys.
Is CVE-2026-62327 being exploited?
Not confirmed. CVE-2026-62327 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.64% probability of exploitation in the next 30 days.
How severe is CVE-2026-62327?
CVE-2026-62327 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62327?
Yes. A fix has been recorded for CVE-2026-62327. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62327 affect?
CVE-2026-62327 affects 9Router ≤ 0.4.41, Next.js API routes using 9Router, Connected AI provider accounts (API keys). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62327?
Block or add auth to /api/usage/stats, update 9Router when patched, rotate exposed API keys, audit usage
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated disclosure of plaintext AI provider API keys enabling account takeover, billing fraud, and quota exhaustion.
Immediate action required
- affected<= 0.4.41
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.