CVE-2026-55500: 9router: Exposure of Sensitive Information and Unprotected Database Import/Export Allows Complete Credential Theft and Database Takeover
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.
Security readout for executives and security teams
Plain-English summary
9router before 0.4.80 exposes a database import/export endpoint that can reveal stored credentials, API keys, OAuth tokens, and settings, or allow database overwrite. This is business-critical for any reachable deployment because compromise could extend into connected services, not just the router itself.
Executive priority
Treat this as urgent for any deployed 9router instance. The vulnerability can expose secrets and enable database takeover, creating downstream risk across systems whose credentials are stored in 9router.
Technical view
CVE-2026-55500 affects decolua 9router versions before 0.4.80. The /api/settings/database endpoint permits full database export and import with only the ALWAYS_PROTECTED JWT or CLI token middleware check. CVSS 3.1 is 9.9 with network access, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to organizations running 9router below 0.4.80 with the API reachable to users or networks where a JWT or CLI token could be obtained or abused.
Exploitation context
The source bundle does not show CISA KEV listing or public active exploitation. Impact is severe because successful abuse can extract secrets and overwrite the database, but no exploit status beyond the advisory is provided.
Researcher notes
Available evidence names CWE-200 and a fixed release, but the bundle does not include detailed exploit telemetry. Validation should focus on version, endpoint exposure, token handling, logs, and whether secrets stored in the database were potentially accessed.
Mitigation direction
Upgrade 9router to version 0.4.80 or later.
Restrict network access to the 9router API and administrative routes.
Review vendor advisory and release notes for any additional hardening guidance.
Rotate stored credentials, API keys, and OAuth tokens if access is suspected.
Back up known-good configuration before applying operational changes.
Validation and detection
Inventory all 9router deployments and confirm versions are 0.4.80 or later.
Identify whether /api/settings/database is reachable from untrusted networks.
Review logs for database export or import activity before patching.
Confirm administrative access controls after upgrade using safe, authorized checks.
Assess whether exposed secrets require revocation or downstream incident review.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.