dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-46339

CRITICAL · 10.0 CVSS v3.1 Published 2026-07-15
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 is an AI router & token saver. From 0.4.30 until 0.4.37, 9Router's src/proxy.js middleware did not protect /api/cli-tools/* and /api/mcp/*, allowing unauthenticated registration of customPlugins through src/app/api/cli-tools/cowork-settings/route.js and command execution through the MCP bridge. This vulnerability is fixed in 0.4.37.

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 versions 0.4.30-0.4.37 have an authentication bypass in src/proxy.js that fails to protect /api/cli-tools/* and /api/mcp/* endpoints. This allows unauthenticated attackers to register customPlugins via the cowork-settings route and execute arbitrary commands through the MCP bridge.

MitigationUpgrade to version 0.4.37 or later. If immediate patching is not possible, implement authentication middleware on the /api/cli-tools/* and /api/mcp/* routes to block unauthenticated access.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 9Router installation and version
    Locate the 9Router installation and retrieve its version number (commonly via 'npm list 9router', package.json, or the application's --version flag)
    Affected if The installed version falls within 0.4.30 to 0.4.37 inclusive
  2. Locate src/proxy.js
    Find the src/proxy.js file within the 9Router installation directory
    Affected if The file exists and contains routes for /api/cli-tools/* or /api/mcp/* without authentication middleware
  3. Verify authentication on vulnerable endpoints
    Send unauthenticated HTTP requests to /api/cli-tools/* and /api/mcp/* endpoints (e.g., using curl or a browser) to confirm they are accessible without credentials
    Affected if These endpoints respond successfully without requiring authentication
  4. Check for customPlugin registration exposure
    Inspect whether the cowork-settings route allows unauthenticated registration of customPlugins via the MCP bridge
    Affected if The cowork-settings route accepts customPlugin definitions without authentication validation

You are affected if 9Router version is between 0.4.30-0.4.37 AND the /api/cli-tools/* or /api/mcp/* endpoints are accessible without authentication, allowing unauthenticated customPlugin registration.

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

Upgrade to version 0.4.37 or later. If immediate patching is not possible, implement authentication middleware on the /api/cli-tools/* and /api/mcp/* routes to block unauthenticated access.

Recommended fix Moderate confidence

9Router version 0.4.37 or later

  1. 1. Identify the current version of 9Router by checking package.json or running 'npm list 9router' or the application's version command
  2. 2. If the installed version is between 0.4.30 and 0.4.37 (inclusive of 0.4.30, exclusive of 0.4.37), the system is vulnerable
  3. 3. Upgrade to version 0.4.37 or later by running 'npm install 9router@latest' or 'npm install [email protected]'
  4. 4. Restart the 9Router service to apply the update
  5. 5. Verify the upgrade was successful by checking the new version number
  6. 6. Test that the /api/cli-tools/* and /api/mcp/* endpoints now require authentication (if applicable)
Caveat Review release notes between your current version and 0.4.37 for any breaking changes in behavior or API

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46339 — 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-46339 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