← Back to results
Vulnerability record · public intelligence
CVE-2026-55642
CRITICAL

dbx: Unauthenticated arbitrary SQL execution in dbx-web (authentication fails open when no password is configured)

Published Aug 20, 2026 · Updated Oct 24, 2026

Severity · CVSSCRITICAL · 9.8
Known exploitationNot listed
EPSS / likelihood0.69%
QFinch risk score20 / 100

Original summary

Normalized public record · Updated Oct 24, 2026

dbx: Unauthenticated arbitrary SQL execution in dbx-web (authentication fails open when no password is configured)

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
MEDIUM
Confidence
20%
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Patch commit ↗
  4. Source repository ↗

Record history

Published Aug 20, 2026 · Last refreshed Oct 24, 2026