CVE-2026-55500: 9router 9routers Has Exposure Of Sensitive Vulnerability
CRITICALCVE-2026-55500 is a CRITICAL (CVSS 9.9) 9routers has exposure of sensitive vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting 9router libraries in the npm ecosystem. The issue involves 9routers has exposure of sensitive information and unprotected database import/export, allowing complete credential theft and database takeover. Remediation is available in the latest vendor maintenance releases.
CVE-2026-55500 at a Glance
Security Impact
CVSS: 9.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).
How to Fix CVE-2026-55500
To remediate this vulnerability, upgrade all affected 9router dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install 9router@Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls 9router
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-55500, inspect your project dependencies using npm:
npm ls 9router
Analyze the terminal output to locate any version of 9router in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The npm ls 9router command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In 9router, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-55500 Affected 9router Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
9router
|
npm |
≤ 0.4.71
|
|
References
Frequently Asked Questions
What is CVE-2026-55500?
Which 9router versions are affected?
What version fixes CVE-2026-55500?
Is 9router affected?
What is the CVSS score of CVE-2026-55500?
What CWE is associated with CVE-2026-55500?
How can I check npm dependencies for CVE-2026-55500?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-qvfm-67h2-2qfx",
"modified" : "2026-07-06T21:37:49Z",
"published" : "2026-07-06T21:37:49Z",
"aliases" : [ "CVE-2026-55500" ],
"summary" : "9routers has Exposure of Sensitive Information and Unprotected Database Import/Export, Allowing Complete Credential Theft and Database Takeover",
"details" : "## Summary\n\nThe `/api/settings/database` endpoint allows full database export (containing all credentials, API keys, OAuth tokens, and settings) and full database import (complete overwrite) without any authentication requirement beyond the `ALWAYS_PROTECTED` middleware check, which only validates JWT or CLI token. Combined with other vulnerabilities (e.g., default password, tunnel exposure), this enables complete database takeover.\n\n## Description\n\nThe endpoint `/api/settings/database` is listed in `ALWAYS_PROTECTED` in `dashboardGuard.js` (line 42), which requires a valid JWT token or CLI token. However, this protection is insufficient because:\n\n1. **GET (Export):** Returns the complete database including API keys (`key` field in `apiKeys` table), OAuth tokens, and all provider credentials. Line 80 in `src/lib/db/index.js`: `apiKeys: db.all(\"SELECT * FROM apiKeys\").map(...)` — the `key` field contains the plaintext API key value.\n\n2. **POST (Import):** Accepts arbitrary JSON and performs a complete database wipe-and-replace in a transaction (lines 102-163 in `src/lib/db/index.js`). This replaces all settings including the password hash, effectively allowing an attacker to set their own password.\n\n3. The exported data includes `apiKeys` with their plaintext `key` values, `providerConnections` with all OAuth tokens, and `settings` with OIDC client secrets.\n\n### Evidence\n\n**File:** `src/app/api/settings/database/route.js`\n```javascript\nexport async function GET() {\n const payload = await exportDb();\n return NextResponse.json(payload);\n}\n\nexport async function POST(request) {\n const payload = await request.json();\n await importDb(payload);\n // ...\n}\n```\n\n**File:** `src/lib/db/index.js` (lines 96-163)\n```javascript\nexport async function importDb(payload) {\n db.transaction(() => {\n // Wipe all tables\n db.run(`DELETE FROM settings`);\n db.run(`DELETE FROM providerConnections`);\n db.run(`DELETE FROM providerNodes`);\n db.run(`DELETE FROM proxyPools`);\n db.run(`DELETE FROM apiKeys`);\n db.run(`DELETE FROM combos`);\n db.run(`DELETE FROM kv WHERE scope IN (...)`);\n // Then insert attacker-controlled data\n // ...\n });\n}\n```\n\nThe `exportDb` function at line 80 exposes API key plaintext:\n```javascript\napiKeys: db.all(`SELECT * FROM apiKeys`).map((r) => ({ \n id: r.id, key: r.key, name: r.name, ...\n})),\n```\n\n## Steps to Reproduce\n\n1. Authenticate with any valid JWT (e.g., using the default password \"123456\")\n2. Export: `curl -b auth_token=<jwt> http://localhost:20128/api/settings/database`\n3. Observe: Full database dump with all credentials in plaintext\n4. Import malicious data: `curl -X POST -b auth_token=<jwt> -H \"Content-Type: application/json\" -d '<modified-db>' http://localhost:20128/api/settings/database`\n5. All settings, passwords, API keys are now replaced with attacker-controlled values\n\n## Impact\n\n- **Confidentiality:** Complete exposure of all stored secrets (API keys, OAuth tokens, OIDC client secrets)\n- **Integrity:** Complete database replacement with attacker-controlled data\n- **Availability:** Database wipe is possible by importing an empty database\n- **Scope Changed:** Importing new settings affects all users and downstream services\n\n## Recommended Fix\n\n1. Require re-authentication for database export/import (not just an existing session)\n2. Mask/redact API keys in export (or require explicit opt-in for key export)\n3. Add confirmation step for import (require current password verification)\n4. Implement database backup before import\n5. Log all export/import operations with audit trail",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "9router"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "0.4.71"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/decolua/9router/security/advisories/GHSA-qvfm-67h2-2qfx"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/decolua/9router"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-06T21:37:49Z",
"nvd_published_at" : null
}
}