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.

CVE-2026-55642 affects dbx, a cross-platform database client, in versions prior to 0.5.51. The vulnerability exists in the dbx-web component where the auth_middleware in auth.rs bypasses authentication entirely when password_hash is None. This condition occurs on fresh deployments where DBX_PASSWORD is unset and no stored password exists. Since the service binds to 0.0.0.0 on port 4224 by default, an unauthenticated remote attacker can access the /api/connection/connect and /api/query/execute API routes. Exploitation allows the attacker to leverage configured database credentials to execute arbitrary SQL commands, enabling data disclosure, modification, or destruction. The desktop Tauri application variant is not affected as it binds only to the loopback interface. The issue has been patched in version 0.5.51.