CVE-2026-62328
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited9Router through version 0.4.41 contain an unauthenticated information disclosure vulnerability that 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 by querying the request-logs and request-details API routes which lack authentication middleware.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidence9Router versions through 0.4.41 expose unauthenticated API endpoints (request-logs and request-details) that allow remote attackers to access sensitive user data including complete AI conversation histories with system prompts, user messages, assistant responses, tool calls, and user email addresses through paginated request enumeration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify 9Router installation and versionLocate the 9Router application and determine its installed version by checking the application binary, package manager, or configuration file. Compare the version number against the affected range (any version through 0.4.41).Affected if 9Router version is 0.4.41 or lower, or if the version cannot be determined but the product is present.
-
Verify API endpoint exposureIdentify the network service or web server hosting 9Router. Use a web browser or HTTP client to attempt access to the /api/request-logs and /api/request-details endpoints without providing any authentication credentials.Affected if The endpoints respond with HTTP 200 or other success status codes rather than redirecting to a login page or returning 401/403 authentication errors.
-
Confirm sensitive data accessibilityOn the identified endpoints, attempt to access paginated data by manipulating query parameters such as page, offset, or limit. Examine the response payload to determine if it contains user conversation histories, system prompts, user messages, assistant responses, tool calls, or email addresses.Affected if The API returns JSON or other structured data containing AI conversation content, system prompts, or user PII without requiring authentication tokens or session cookies.
-
Check authentication configurationReview the 9Router configuration files, middleware settings, or routing definitions to confirm whether authentication middleware is explicitly applied to the /api/request-logs and /api/request-details routes.Affected if No authentication middleware (such as token validation, session checks, or login requirements) is configured for these routes.
A user is affected if 9Router version 0.4.41 or lower is running and the /api/request-logs or /api/request-details endpoints are accessible without authentication and return sensitive user data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAdd authentication middleware to the request-logs and request-details API routes, and conduct a broader audit to identify any other unprotected endpoints that may expose sensitive data.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-62328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data