dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-59801

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

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 · unedited
9Router through version 0.4.41 contains an unauthenticated access vulnerability that allows remote attackers to interact with provider management API endpoints by sending requests without any credentials due to missing authentication middleware in the Next.js API routes under src/app/api/providers/*. Attackers can enumerate, create, modify, or delete provider connections to expose partial credentials, OAuth tokens, and API keys, redirect AI traffic to attacker-controlled servers, or cause complete denial of service by deleting all provider connections.

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 confidence

9Router through v0.4.41 has a critical authentication bypass in its Next.js API routes under src/app/api/providers/*. The provider management endpoints lack authentication middleware, allowing unauthenticated remote attackers to enumerate, create, modify, or delete provider connections. This exposes OAuth tokens, API keys, and credentials, enables AI traffic redirection to attacker-controlled servers, or permits complete DoS via mass deletion of provider connections.

MitigationImmediately add authentication middleware to all src/app/api/providers/* routes to enforce credential validation. Audit existing provider configurations for compromise, rotate any exposed credentials/tokens, and implement rate limiting to prevent enumeration and DoS.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed 9Router version
    Check package.json, git tags, or run 'npm list 9router' in the project root directory
    Affected if Version is v0.4.41 or earlier (any version up to and including this release)
  2. Verify provider API routes exist
    List or access the src/app/api/providers/ directory - look for route.js, route.ts, or similar endpoint handler files
    Affected if The src/app/api/providers/* endpoint files exist in the installation
  3. Inspect authentication on provider endpoints
    Open src/app/api/providers/* route files and search for authentication middleware imports or calls (such as auth, verifyToken, requireAuth, session validation)
    Affected if No authentication middleware is present in the provider API route handlers
  4. Check for credential exposure in responses
    Make a test request to the provider API endpoints (e.g., GET /api/providers) without providing any credentials and inspect the response for returned OAuth tokens, API keys, or plaintext credentials
    Affected if The API returns sensitive provider credentials without authentication
  5. Audit provider connections for unauthorized entries
    Query the provider configuration storage (database or config files) to list all configured providers and check for unknown or attacker-controlled server URLs
    Affected if Unexpected provider connections exist pointing to unknown or attacker-controlled servers

A user is affected if running 9Router v0.4.41 or earlier AND the src/app/api/providers/* routes are present AND lack authentication middleware, allowing unauthenticated access to provider credentials and configurations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately add authentication middleware to all src/app/api/providers/* routes to enforce credential validation. Audit existing provider configurations for compromise, rotate any exposed credentials/tokens, and implement rate limiting to prevent enumeration and DoS.

Recommended fix Moderate confidence

9Router version 0.4.42 or later

  1. 1. Identify the current installed version of 9Router by checking the package.json or version file in the deployment environment
  2. 2. Stop any running instances of 9Router to prevent continued exploitation during the upgrade process
  3. 3. Backup the current configuration and any provider connection data to preserve settings
  4. 4. Upgrade to 9Router version 0.4.42 or later (the first version containing the fixed authentication middleware)
  5. 5. Verify that the upgrade completed successfully by checking the new version number
  6. 6. Restart the 9Router service
  7. 7. Test that authentication is now properly enforced on the provider management API endpoints under src/app/api/providers/ by attempting an unauthenticated request and confirming it is rejected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,768.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59801 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59801 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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