dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-55500

CRITICAL · 9.9 CVSS v3.1 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 6 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. Prior to 0.4.80, the /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. This issue is fixed in version 0.4.80.

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

The /api/settings/database endpoint in 9Router versions prior to 0.4.80 allows unauthenticated export of the entire database containing credentials, API keys, and OAuth tokens, as well as unauthenticated full database import/overwrite. The ALWAYS_PROTECTED middleware only validates JWT or CLI tokens but fails to enforce proper authentication for these highly sensitive operations.

MitigationUpgrade to version 0.4.80 or later which contains the fix. Alternatively, implement proper authentication and authorization controls on the /api/settings/database endpoint before deployment.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Determine 9Router version
    Locate the installed 9Router version number using the system's package manager, configuration file, or running '9router --version' if available
    Affected if The installed version is prior to 0.4.80 (e.g., 0.4.79, 0.4.70, etc.)
  2. Verify endpoint exposure
    Attempt to access the /api/settings/database endpoint via HTTP request without providing any authentication credentials
    Affected if The endpoint responds with database export/import functionality rather than returning an authentication error (401/403)
  3. Check ALWAYS_PROTECTED middleware configuration
    Inspect the middleware configuration files or source code to confirm ALWAYS_PROTECTED is applied to the /api/settings/database route
    Affected if The middleware is present but fails to enforce JWT or CLI token validation for this endpoint
  4. Test unauthenticated database export
    Send a GET request to /api/settings/database to retrieve the database export without authentication headers
    Affected if The request succeeds and returns database contents including credentials, API keys, or OAuth tokens
  5. Confirm authentication enforcement
    Review server logs or test with invalid/expired JWT or CLI tokens to verify proper rejection of unauthenticated requests
    Affected if Requests without valid authentication are allowed through instead of being rejected

A user is affected if running 9Router version prior to 0.4.80 and the /api/settings/database endpoint is accessible without valid JWT or CLI token authentication.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.4.80 or later which contains the fix. Alternatively, implement proper authentication and authorization controls on the /api/settings/database endpoint before deployment.

Recommended fix Moderate confidence

9Router version 0.4.80

  1. 1. Identify the current version of 9Router by checking the installed instance or configuration
  2. 2. Download 9Router version 0.4.80 or later from the official GitHub repository
  3. 3. Apply the upgrade following the standard upgrade procedure for 9Router
  4. 4. Verify the /api/settings/database endpoint now requires proper authentication beyond the ALWAYS_PROTECTED middleware check
  5. 5. Confirm the database export/import functionality is no longer accessible without valid authentication

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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