# CVE-2026-62327: 9Router 0.4.41 - Unauthenticated API Key Exposure via /api/usage/stats

> Unauthenticated attackers can retrieve plaintext API keys and usage data from the /api/usage/stats endpoint, leading to unauthorized account access and billing fraud.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-7gvh-h32g-9cfw

## What is CVE-2026-62327?

CVE-2026-62327 is a critical vulnerability in decolua 9Router, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-62327?


## How do I fix CVE-2026-62327?

No fix has been published for CVE-2026-62327 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62327 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62327 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62327 and fix it if it is affected.

What it is: CVE-2026-62327 is a critical vulnerability in decolua 9Router, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62327 exists.

Affected product: decolua 9Router. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62327/ (Markdown: https://insights.sbomify.com/CVE-2026-62327/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62327
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62327
- OSV: https://osv.dev/vulnerability/CVE-2026-62327

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62327/
Summaries are generated and may contain mistakes; the official description above is the record.