t8y2 dbx up to 0.5.50 auth_middleware auth.rs password_hash improper authentication

Summaryinfo

A vulnerability was found in t8y2 dbx up to 0.5.50. It has been classified as critical. Impacted is an unknown function of the file crates/dbx-web/src/auth.rs of the component auth_middleware. Performing a manipulation of the argument password_hash results in improper authentication. This vulnerability was named CVE-2026-55642. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in t8y2 dbx up to 0.5.50. It has been classified as critical. This affects an unknown code block of the file crates/dbx-web/src/auth.rs of the component auth_middleware. The manipulation of the argument password_hash with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-55642 since 06/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 0.5.51 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• t8y2

Name

• dbx

Version

• 0.5.0
• 0.5.1
• 0.5.2
• 0.5.3
• 0.5.4
• 0.5.5
• 0.5.6
• 0.5.7
• 0.5.8
• 0.5.9
• 0.5.10
• 0.5.11
• 0.5.12
• 0.5.13
• 0.5.14
• 0.5.15
• 0.5.16
• 0.5.17
• 0.5.18
• 0.5.19
• 0.5.20
• 0.5.21
• 0.5.22
• 0.5.23
• 0.5.24
• 0.5.25
• 0.5.26
• 0.5.27
• 0.5.28
• 0.5.29
• 0.5.30
• 0.5.31
• 0.5.32
• 0.5.33
• 0.5.34
• 0.5.35
• 0.5.36
• 0.5.37
• 0.5.38
• 0.5.39
• 0.5.40
• 0.5.41
• 0.5.42
• 0.5.43
• 0.5.44
• 0.5.45
• 0.5.46
• 0.5.47
• 0.5.48
• 0.5.49
• 0.5.50

Website

• Product: https://github.com/t8y2/dbx/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion