Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-62327 – Unauthenticated AI Provider API Key Disclosure – 9Router through v0.4.41

Be the first to know when new zero-days emerge:

Summary

CVE-2026-62327 is a critical unauthenticated information disclosure vulnerability in 9Router (by decolua), a self-hosted Next.js-based AI provider routing dashboard, affecting all versions through 0.4.41. The flaw allows any remote attacker to retrieve full plaintext API keys for all connected AI provider accounts by sending a single unauthenticated HTTP request to the /api/usage/stats endpoint. With a CVSS 4.0 score of 9.3 (and a CVSS 3.1 score of 10.0), exploitation requires no credentials, no privileges, and no user interaction.

Technical details

  • Root cause: Authentication middleware in middleware.ts fails to intercept and enforce session validation on the /api/usage/stats Next.js API route. Additionally, provider credentials are serialized and returned in API responses without any field filtering, directly exposing raw key strings.
  • Trigger conditions: The vulnerability is exploitable whenever a 9Router instance is reachable over a network. The application’s built-in tunnel functionality — a documented feature — enables public internet exposure of otherwise local deployments, widening the attack surface.
  • Attack vector: A single unauthenticated HTTP GET request to /api/usage/stats on any network-accessible 9Router instance is sufficient to exploit the vulnerability; no exploit tooling or chaining is required.
  • Impact: The response returns full plaintext API keys for all connected AI provider accounts, alongside token usage counts, cost breakdowns, and request metadata. Exploitation enables unauthorized use of connected AI services, billing fraud, and quota exhaustion against the affected organization’s provider accounts.

Affected software

  • 9Router (npm package 9router, by decolua): all versions through and including 0.4.41

Severity

  • CVSS 4.0 Score: 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
  • CVSS 3.1 Score: 10.0 — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
  • CWE-306: Missing Authentication for Critical Function
  • CWE-862: Missing Authorization
  • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Mitigation and recommended actions

  • Immediate patch: Upgrade 9Router to version 0.4.45 or later, which introduces session validation via getServerSession() on the affected API routes and removes unfiltered credential serialization.
  • Mandatory key rotation: All AI provider API keys (OpenAI, Anthropic, and any other configured providers) entered into the dashboard prior to patching must be treated as compromised and rotated immediately across all connected provider accounts.
  • Network mitigation (if immediate patching is not feasible): Disable any tunnel or external-access configuration to restrict the 9Router dashboard to localhost-only access until the patch is applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge