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

Back
New CVE Detected

CVE-2026-62328 – Unauthenticated Information Disclosure – 9Router ≤ 0.4.41

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-62328 is a high-severity unauthenticated information disclosure vulnerability in 9Router (by decolua), a self-hosted AI model routing proxy used to connect AI coding tools (such as Claude Code, Cursor, Codex, and Copilot) to upstream AI providers. The flaw arises from missing authentication middleware on two API endpoints, enabling any unauthenticated remote attacker to enumerate and retrieve complete AI conversation histories and associated user data. It carries a CVSS 4.0 score of 8.7 (High) and affects all 9Router versions through 0.4.41.

Technical details

  • Root cause: The /api/usage/request-logs and /api/usage/request-details API routes in 9Router’s Next.js dashboard lack authentication middleware entirely (CWE-862: Missing Authorization; CWE-359: Exposure of Private Personal Information to an Unauthorized Actor). Requests to these routes are served without any credential or session check.
  • Trigger conditions: No authentication, no user interaction, and no special preconditions are required. An attacker only needs network access to the exposed 9Router instance.
  • Attack vector: Remote, over the network (AV:N). An attacker sends unauthenticated HTTP GET requests to the paginated /api/usage/request-logs endpoint to enumerate all request records, then fetches individual records via /api/usage/request-details/:id.
  • Impact: Full exposure of AI conversation histories across all users of the instance, including system prompts, user messages, assistant responses, tool calls, and user email addresses. This constitutes a significant confidentiality breach (VC:H) for any organization routing sensitive development or business queries through an internet-exposed 9Router deployment.

Affected software

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

Severity

  • CVSS v3.1 Base Score: 7.5 (High)
  • CVSS v3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate – no patch available: As of the publication of the vendor’s security advisory (GHSA-vjc7-jrh9-9j86), no patched version has been released for this specific vulnerability. Organizations should not wait for a patch before acting.
  • Network isolation: Restrict access to 9Router instances using firewall rules so that the service is reachable only from trusted internal IP ranges or via VPN. Do not expose the 9Router dashboard or its API on a publicly routable address.
  • Localhost binding: If 9Router is not required to serve remote clients, ensure it is bound to localhost (127.0.0.1) rather than 0.0.0.0.
  • Monitor for vendor updates: Follow the decolua/9router GitHub repository and its security advisories page for patches as they are released.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge