CVE-2026-55642

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

dbx is a cross-platform database client for databases. Prior to 0.5.51, dbx-web auth_middleware in crates/dbx-web/src/auth.rs passes every protected request to the handler chain when password_hash is None. A fresh deployment reaches that state when DBX_PASSWORD is unset and no stored password exists, while crates/dbx-web/src/main.rs binds the service to 0.0.0.0 on port 4224 by default. An unauthenticated network attacker can call the /api/connection/connect and /api/query/execute routes to use configured database credentials and execute arbitrary SQL, allowing disclosure, modification, or destruction of data in connected databases. The desktop Tauri application is not affected because it binds only to loopback. This issue is fixed in version 0.5.51.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 20, 2026

Last Modified

August 20, 2026

Advisory Details (4)

Auto-updated Aug 27, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Unauthenticated arbitrary SQL execution in dbx-web (authentication fails open when no password is configured) · Advisory · t8y2/dbx · GitHub

https://github.com/t8y2/dbx/security/advisories/GHSA-rqp4-8fxh-22vh
github_release Patch Available

v0.5.51

Patch available: t8y2/dbx v0.5.51

https://github.com/t8y2/dbx/releases/tag/v0.5.51
generic

Docker Web 密码认证对 MCP 连接无效,可绕过认证直接操作数据库 · Issue #2887 · t8y2/dbx · GitHub

https://github.com/t8y2/dbx/issues/2887
github_commit

commit fb919efe0a62 (t8y2/dbx)

Fix landed in t8y2/dbx commit fb919efe0a62 — awaiting tagged release

https://github.com/t8y2/dbx/commit/fb919efe0a62869631f49242d1f4fe8d41718c2a

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-30 01:29 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 01:28 UTCEG score recompute
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 15:51 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 16:24 UTCEG score recompute
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 16:58 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 17:35 UTCEG score recompute
  12. 2026-08-24 09:50 UTCEG score recompute
  13. 2026-08-23 02:38 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 03:21 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-20 20:20 UTCEG score recompute
  18. 2026-08-20 19:37 UTCEG score recompute
  19. 2026-08-20 17:33 UTCEG score recompute
  20. 2026-08-20 16:52 UTCEG score recompute
  21. 2026-08-20 16:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55642?
CVE-2026-55642 is a critical vulnerability published on August 20, 2026. dbx is a cross-platform database client for databases. Prior to 0.5.51, dbx-web authmiddleware in crates/dbx-web/src/auth.rs passes every protected request to the handler chain when passwordhash is None. A fresh deployment reaches that state when DBX_PASSWORD is unset and no stored password exists,…
When was CVE-2026-55642 disclosed?
CVE-2026-55642 was first published in the National Vulnerability Database on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55642 actively exploited?
CVE-2026-55642 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.0% of all scored CVEs.
What is the CVSS score of CVE-2026-55642?
CVE-2026-55642 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-55642?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55642, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55642

Explore →

Is Your Infrastructure Affected by CVE-2026-55642?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.