Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-55642 – Unauthenticated Remote SQL Execution (Authentication Bypass) – dbx-web (t8y2/dbx) p

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-55642 is a critical (CVSS 9.8) authentication bypass in dbx, a cross-platform database client. The dbx-web component’s authentication middleware fails open and passes every protected API request through when no password has been configured, letting unauthenticated network attackers execute arbitrary SQL against connected databases. The flaw affects all versions of dbx-web prior to 0.5.51.

Technical details

  • Root cause: The auth_middleware in crates/dbx-web/src/auth.rs passes every protected request to the handler chain whenever password_hash is None.
  • Trigger conditions: A fresh deployment reaches this state when the DBX_PASSWORD environment variable is unset and no stored password exists yet; crates/dbx-web/src/main.rs binds the service to 0.0.0.0 on port 4224 by default, exposing it to the network.
  • Attack vector: Network, no authentication or user interaction required. An attacker sends requests to /api/connection/connect and /api/query/execute to leverage the configured database credentials.
  • Impact: Full disclosure, modification, or destruction of data in any database connected to the exposed dbx-web instance.
  • Not affected: The desktop Tauri application variant, which binds only to loopback.

Affected software

  • dbx-web (t8y2/dbx), all versions prior to 0.5.51

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CWE-306: Missing Authentication for Critical Function

Mitigation and recommended actions

  • Immediate: Upgrade dbx-web to version 0.5.51 or later, which enforces authentication and returns HTTP 401 on API routes until a password is set.
  • If patching is not immediately possible:
    • Set the DBX_PASSWORD environment variable before starting the service so a password hash is always configured.
    • Do not expose dbx-web directly on 0.0.0.0/the public internet; bind it to localhost or restrict access via firewall/network segmentation.
    • Place the service behind a network control (VPN, allow-list, or reverse proxy requiring authentication) until upgraded.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: DBX
  • Raw response body: dbx-startup-theme, /connection-dialog-legacy.css

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge