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.
CVE-2026-55500
“—” beside the score: it is equal to the CVSS score beside it.
Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-06. A secondary CVSS source baseline 9.9; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.9
- EG Score
- 9.9CRITICALmedium confidence
- EG Risk
- 45EG Risk 45/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity99% × 45%The EG Score, 9.9 of 10.Exploitation0.7% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.7%
- EPSS %ILE
- 51st
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
July 6, 2026
Last Modified
July 10, 2026
Advisory Details (3)
Auto-updated Oct 10, 2026Exposure of Sensitive Information and Unprotected Database Import/Export Allows Complete Credential Theft and Database Takeover · Advisory · decolua/9router · GitHub
https://github.com/decolua/9router/security/advisories/GHSA-qvfm-67h2-2qfxfeat: Vercel AI Gateway, MiMo Free, Kiro failover + security & provider fixes version 0.4.80
Patch available: decolua/9router v0.4.80
https://github.com/decolua/9router/releases/tag/v0.4.80commit 0c7c9de00ae3 (decolua/9router)
Patch available: decolua/9router v0.4.80 (contains commit 0c7c9de00ae3)
https://github.com/decolua/9router/commit/0c7c9de00ae3ab81d6580e3cc368483c4c03f6fdVendor Advisories for CVE-2026-55500(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | 9router | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| 9router | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 46× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 391 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 291 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-12 06:52 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-10-11 19:39 UTCEG score recompute
- 2026-10-11 16:54 UTCEG score recompute
- 2026-10-11 14:17 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-28 13:40 UTCEG score recompute
- 2026-09-28 13:40 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-23 11:00 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
Show 75 moreShow fewer
- 2026-09-23 06:21 UTCEG score recompute
- 2026-09-23 06:21 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-18 10:11 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-18 05:55 UTCEG score recompute
- 2026-09-18 05:55 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-14 08:05 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-14 03:58 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-13 23:55 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-13 16:48 UTCEG score recompute
- 2026-09-13 16:48 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-13 12:44 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-13 08:36 UTCEG score recompute
- 2026-09-13 08:36 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-12 13:36 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-12 03:46 UTCEG score recompute
- 2026-09-12 03:46 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-06 14:09 UTCEG score recompute
- 2026-09-06 14:09 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-06 03:01 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-05 22:56 UTCEG score recompute
- 2026-09-05 22:56 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-31 01:15 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-30 21:11 UTCEG score recompute
- 2026-08-30 21:11 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-30 17:07 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-30 13:03 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-30 07:58 UTCEG score recompute
- 2026-08-30 07:58 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-08-28 02:44 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-27 21:57 UTCEG score recompute
- 2026-08-27 21:57 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-08-27 02:06 UTCEG score recompute
- 2026-08-27 02:05 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-08-26 13:53 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-25 16:01 UTCEG score recompute
- 2026-08-25 16:01 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-08-25 11:56 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-25 04:51 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-25 00:47 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-24 20:44 UTCEG score recompute
- 2026-08-24 20:44 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-24 13:56 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-24 09:53 UTCEG score recompute
- 2026-08-24 09:53 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-24 04:05 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-23 23:06 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-23 18:33 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-23 14:29 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-23 10:26 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-23 06:08 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-23 02:03 UTCEG score recompute
- 2026-08-23 02:03 UTCGHSA enrichmentGHSA-qvfm-67h2-2qfx · GitHub severity CRITICAL · GitHub CVSS 9.9
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Related CVEs(same product + same CWE)
Same product
10 shownnpm:9router
Frequently asked(5)
What is CVE-2026-55500?
When was the CVE record for CVE-2026-55500 published?
Is CVE-2026-55500 actively exploited?
What is the CVSS score of CVE-2026-55500?
How do I remediate CVE-2026-55500?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55500
Is Your Infrastructure Affected by CVE-2026-55500?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.