Summary
CVE-2026-53459 is a critical fail-open authentication bypass in Bambuddy, a self-hosted print archive and management system for Bambu Lab 3D printers. When database access fails — including as a result of resource exhaustion triggered by an attacker — the authentication middleware fails open and grants unauthenticated access to all protected endpoints. The vulnerability carries a CVSS score of 9.3 (Critical).
Technical details
- Root cause: Bambuddy’s authentication code is classified under CWE-636 (Not Failing Securely / "Failing Open") and CWE-755 (Improper Handling of Exceptional Conditions) — when the backend cannot reach or query its database to validate a session/token, it falls back to allowing the request instead of denying it.
- Trigger condition: An attacker can deliberately flood a public (unauthenticated) endpoint to exhaust backend resources, causing the database access used for authentication checks to fail.
- Attack vector: Network — no credentials, privileges, or user interaction are required. The attack works over any network path from which the Bambuddy instance is reachable (LAN, VPN/Tailscale, port-forwarded internet, reverse-proxied, containerized, or bare-metal deployments).
- Impact: Once the fail-open condition is triggered, an unauthenticated attacker gains full access to every protected endpoint of the Bambuddy instance, resulting in unauthorized data access and manipulation within the print archive and management system. Both authentication-enabled and authentication-disabled installations expose the vulnerable code path.
Affected software
- Bambuddy (maziggy/bambuddy), versions 0.1.6 up to and including 0.2.4.3
Severity
- CVSS v4.0 Base Score: 9.3 (Critical)
- Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: Upgrade Bambuddy to version 0.2.4.4 or later, where the authentication middleware has been fixed to fail closed on database errors.
- If no patch can be applied immediately: Restrict network exposure of the Bambuddy instance — do not expose it directly to untrusted networks or the public internet, and place it behind network-level access controls until the upgrade can be completed. No other vendor-recommended workaround exists; upgrading is the only complete remediation.

