Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 10.0amended

9router has unauthenticated CRUD on /api/providers and Full API Key Leak via /api/usage/stats

CVE-2026-59801GHSA-vjc7-jrh9-9j86

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm 9router

    Affected
    <= 0.4.41
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-59801: 2.62% estimated exploitation activity in the next 30 days; percentile 85.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
  • CVE-2026-62327: 6.27% estimated exploitation activity in the next 30 days; percentile 93.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
  • CVE-2026-62328: 0.46% estimated exploitation activity in the next 30 days; percentile 39.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

--- title: Unauthenticated CRUD on /api/providers and Full API Key Leak via /api/usage/stats product: 9Router version: <= 0.4.41 severity: critical cverequest: true --- Summary Multiple critical API security vulnerabilities were discovered in 9Router's Next.js dashboard. The /api/providers endpoints lack authentication entirely, allowing anyone to create, read, update, and delete provider connections. Additionally, /api/usage/stats exposes full plaintext API keys, and /api/usage/request-logs + /api/usage/request-details expose all users' request history and full conversation contents (including system prompts, user messages, assistant responses) without authentication. Affected Endpoints | Endpoint | Method | Issue | |---|---|---| | /api/providers | GET | Lists all provider connections with partial credentials, OAuth tokens, account IDs | | /api/providers/:id | GET | Read any single provider detail (IDOR) | | /api/providers | POST | Create arbitrary provider connections with…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-vjc7-jrh9-9j86

  2. Revision 2 · amended ·

    Amended from osv record GHSA-vjc7-jrh9-9j86

  3. Revision 1 · created ·

    Published from ghsa record GHSA-vjc7-jrh9-9j86

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-59801

Advisory: 9router has unauthenticated CRUD on /api/providers and Full API Key Leak via /api/usage/stats
IDs: CVE-2026-59801, GHSA-vjc7-jrh9-9j86
Record: https://patchnext.com/advisories/ghsa-vjc7-jrh9-9j86 (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm 9router: affected <= 0.4.41

## Suggested inspection (read-only)
- `npm ls 9router --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on 9router.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vjc7-jrh9-9j86 (GitHub-reviewed advisory GHSA-vjc7-jrh9-9j86 lists affected ranges: npm 9router >=0 <=0.4.41)
- Verified: https://osv.dev/vulnerability/GHSA-vjc7-jrh9-9j86 (OSV record GHSA-vjc7-jrh9-9j86 lists affected ranges: npm 9router >=0 <=0.4.41)

Commands are suggestions: review each one before running it.

Loading voting…