CVE-2026-25505: maziggy bambuddy · Missing Authentication
Affects maziggy bambuddySource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.1.7 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.1.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade bambuddy and maziggy/bambuddy to 0.1.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| maziggybambuddy | Affected
| Fixed in
|
GitHubmaziggy/bambuddypkg:github/maziggy/bambuddyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-25505, European organizations should immediately upgrade bambuddy installations to version 0.1.7 or later, where the vulnerability is patched. If upgrading is temporarily not feasible, restrict network access to bambuddy services by implementing strict firewall rules and network segmentation to limit exposure to trusted users only. Conduct thorough audits of bambuddy API usage logs to detect any unauthorized access attempts. Rotate any JWT signing keys and secrets used in the environment to invalidate potentially compromised tokens. Employ Web Application Firewalls (WAFs) with custom rules to block suspicious API requests targeting ManyAPI routes. Additionally, implement multi-factor authentication (MFA) on management interfaces where possible to add an extra layer of security. Finally, educate relevant personnel about the risks of hardcoded secrets and the importance of secure coding practices to prevent similar vulnerabilities in custom or third-party software.
Description
Bambuddy is a self-hosted print archive and management system for Bambu Lab 3D printers. Prior to version 0.1.7, a hardcoded secret key used for signing JWTs is checked into source code and ManyAPI routes do not check authentication. This issue has been patched in version 0.1.7.
References
- github.com/maziggy/bambuddy/security/advisories/GHSA-gc24-px2r-5qmf (opens in a new tab)
- github.com/maziggy/bambuddy/pull/225 (opens in a new tab)
- github.com/maziggy/bambuddy/commit/a82f9278d2d587b7042a0858aab79fd8b6e3add9 (opens in a new tab)
- github.com/maziggy/bambuddy/commit/c31f2968889c855f1ffacb700c2c9970deb2a6fb (opens in a new tab)
- github.com/maziggy/bambuddy/blob/a9bb8ed8239602bf08a9914f85a09eeb2bf13d15/backend/app/core/auth.py (opens in a new tab)
- github.com/maziggy/bambuddy/blob/main/CHANGELOG.md (opens in a new tab)
- github.com/maziggy/bambuddy/releases/tag/v0.1.7 (opens in a new tab)