CVE-2026-62328: 9Router Information Disclosure Flaw

CVE-2026-62328 Overview

CVE-2026-62328 is an unauthenticated information disclosure vulnerability in 9Router through version 0.4.41. The flaw allows remote attackers to access sensitive user data by sending requests to unprotected API endpoints. Attackers can enumerate paginated request logs and retrieve complete AI conversation histories, including system prompts, user messages, assistant responses, tool calls, and user email addresses. The request-logs and request-details API routes lack authentication middleware, exposing all logged traffic to any network-based attacker. The vulnerability is categorized under [CWE-359] (Exposure of Private Personal Information to an Unauthorized Actor).

Critical Impact
Remote attackers with no credentials can retrieve complete AI conversation histories, system prompts, and user email addresses from any exposed 9Router instance.

Affected Products

9Router versions through 0.4.41
Deployments exposing the request-logs API route
Deployments exposing the request-details API route

Discovery Timeline

2026-07-13 - CVE-2026-62328 published to NVD
2026-07-15 - Last updated in NVD database

Technical Details for CVE-2026-62328

Vulnerability Analysis

The vulnerability resides in the request logging subsystem of 9Router, an AI request routing application. The application persists detailed records of every AI transaction it proxies. These records include full prompt content, tool invocations, model responses, and metadata such as user email addresses. The API endpoints that expose this stored data do not enforce authentication, allowing any client with network reachability to retrieve arbitrary records. Because the endpoints support pagination, an attacker can iterate through the entire log corpus and reconstruct complete conversation histories for every user of the affected instance.

Root Cause

The root cause is the absence of authentication middleware on two administrative API routes: request-logs and request-details. Other routes in 9Router likely enforce authentication, but these endpoints were exposed without any access control. The design flaw falls under [CWE-359] because personally identifiable information and confidential AI interaction data are returned to unauthorized actors.

Attack Vector

Exploitation requires only network access to a vulnerable 9Router instance. An attacker sends HTTP requests to the request-logs endpoint to enumerate log identifiers, then queries request-details for each identifier to retrieve full conversation content. No credentials, user interaction, or elevated privileges are required. Instances exposed to the internet are directly reachable, and internal deployments are exposed to any actor with lateral network access.

No verified proof-of-concept code is available. Refer to the GitHub Security Advisory and the VulnCheck Security Advisory for technical details.

Detection Methods for CVE-2026-62328

Indicators of Compromise

Unauthenticated HTTP requests to /request-logs or /request-details API paths in 9Router access logs
Sequential or paginated enumeration patterns targeting log identifiers from a single source IP
Unusually large outbound response volumes from the 9Router service to external clients
Requests to the affected endpoints originating from IP addresses outside the expected administrator range

Detection Strategies

Review web server and reverse proxy logs for any access to request-logs and request-details routes that did not include a valid session cookie or bearer token
Alert on high-frequency pagination against the affected endpoints, which indicates automated scraping
Correlate access to the vulnerable routes with geolocation or ASN data to identify anomalous administrative access

Monitoring Recommendations

Enable request-level logging on all 9Router API routes, capturing source IP, path, query parameters, and authentication state
Forward 9Router logs to a centralized SIEM for retention and anomaly analysis
Baseline normal administrative traffic to the log endpoints and alert on deviations in volume or source

How to Mitigate CVE-2026-62328

Immediate Actions Required

Upgrade 9Router to a version later than 0.4.41 once a patched release is published by the maintainer
Restrict network access to 9Router administrative endpoints using firewall rules or reverse proxy allow-lists
Rotate any credentials, API keys, or secrets that may have appeared in logged prompts or tool calls
Notify affected users if request logs contain their email addresses or sensitive conversation content

Patch Information

Refer to the GitHub Security Advisory GHSA-vjc7-jrh9-9j86 for the latest patch status and fixed version information from the 9Router maintainer.

Workarounds

Place 9Router behind a reverse proxy that enforces authentication on the request-logs and request-details paths
Block external access to the affected API routes at the network edge using WAF or firewall rules
Disable request logging entirely if the feature is not required, reducing the amount of exposed data
Restrict 9Router to a private network segment reachable only by trusted administrators until a fixed version is deployed

bash

# Example nginx configuration blocking unauthenticated access to the vulnerable routes
location ~ ^/(request-logs|request-details) {
    allow 10.0.0.0/8;
    deny all;
    proxy_pass http://9router_backend;
}