CVE-2026-55642Public exploitNetwork attack vectorHinoki check available

Unauthenticated SQL execution via fail-open auth

Published Aug 20, 2026 · Updated Aug 20, 2026

Missing authentication in dbx-web in t8y2 DBX before 0.5.51 allows remote attackers to execute arbitrary SQL via exposed API routes. The auth_middleware function in crates/dbx-web/src/auth.rs forwards protected API requests when password_hash is None, so an unset DBX_PASSWORD and absent stored password leave connection and query handlers reachable without a session. Exposure is limited to the self-hosted web service, but a fresh deployment binds 0.0.0.0:4224 by default, letting any host that reaches the port use configured database credentials to read, modify, or delete connected data.

CVSS severity9.8
Critical
EPSS probability0.37%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Missing authentication in dbx-web in t8y2 DBX before 0.5.51 allows remote attackers to execute arbitrary SQL via exposed API routes. The auth_middleware function in crates/dbx-web/src/auth.rs forwards protected API requests when password_hash is None, so an unset DBX_PASSWORD and absent stored password leave connection and query handlers reachable without a session. Exposure is limited to the self-hosted web service, but a fresh deployment binds 0.0.0.0:4224 by default, letting any host that reaches the port use configured database credentials to read, modify, or delete connected data.

The record

CVE
CVE-2026-55642
Published
Aug 20, 2026
Updated
Aug 20, 2026
Vendor
t8y2
Product
DBX
Classifications
CWE-306, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.5.51

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

t8y2 · DBXversion=< 0.5.51

Published CVSS scores

9.8GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-306Missing Authentication for Critical Function
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo