# CVE-2026-53459: Bambuddy's authentication fails open on database errors, allowing unauthenticated access to all endpoints

> Attackers can bypass authentication by exhausting database resources, gaining unauthenticated access to all protected endpoints in Bambuddy.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-6mf4-q26m-47pv

## What is CVE-2026-53459?

CVE-2026-53459 is a critical authentication bypass vulnerability in maziggy bambuddy, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bambuddy is a self-hosted print archive and management system for Bambu Lab 3D printers. Starting in version 0.1.6 and prior to version 0.2.4.4, a fail-open in the authentication code allows any attacker to bypass authentication by flooding a public endpoint to exhaust resources causing database access to fail, granting unauthenticated access to all protected endpoints. Version 0.2.4.4 patches the issue.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-636 (Not Failing Securely)

## Which versions are affected by CVE-2026-53459?


## How do I fix CVE-2026-53459?

No fix has been published for CVE-2026-53459 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53459 being exploited?

There is no known exploitation of CVE-2026-53459 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53459 and fix it if it is affected.

What it is: CVE-2026-53459 is a critical authentication bypass vulnerability in maziggy bambuddy, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53459 in the wild and no public exploit code.

Affected product: maziggy bambuddy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53459/ (Markdown: https://insights.sbomify.com/CVE-2026-53459/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53459
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53459
- OSV: https://osv.dev/vulnerability/CVE-2026-53459

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53459/
Summaries are generated and may contain mistakes; the official description above is the record.