{"answers":{"affected":"2 open source packages ship an affected version, including bambuddy. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25505 exists.","fix":"Upgrade bambuddy to 0.1.7 or later.","what":"CVE-2026-25505 is a critical vulnerability in maziggy bambuddy, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25505 and fix it if it is affected.\n\nWhat it is: CVE-2026-25505 is a critical vulnerability in maziggy bambuddy, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25505 exists.\n\nAffected packages and fixed versions:\n- bambuddy (PyPI): affected all versions; fixed in 0.1.7\n- bambuddy (PyPI): affected all versions; fixed in 0.1.7\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25505/ (Markdown: https://insights.sbomify.com/CVE-2026-25505/index.md)","id":"CVE-2026-25505","markdown":"https://insights.sbomify.com/CVE-2026-25505/index.md","name":"CVE-2026-25505","record":{"aliases":["GHSA-gc24-px2r-5qmf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"3D printer management","requires_auth":"none","summary":"Attackers can bypass authentication and access sensitive data due to hardcoded JWT keys and missing auth checks in Bambuddy.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bambuddy","vendor":"bambuddy"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Bambuddy Uses Hardcoded Secret Key + Many API Endpoints do not Require Authentication","id":"CVE-2026-25505","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":2,"n_references":7,"next":{"headline":"MUNGE has a buffer overflow in message unpacking allows key leakage and credential forgery","id":"CVE-2026-25506"},"packages":[{"ecosystem":"PyPI","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"bambuddy","purl":null,"source":"GHSA-gc24-px2r-5qmf"},{"ecosystem":"PyPI","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"bambuddy","purl":"pkg:pypi/bambuddy","source":"GHSA-gc24-px2r-5qmf"}],"prev":{"headline":"iccDEV Has Type Confusion in CIccTagEmbeddedHeightImage::Validate()","id":"CVE-2026-25503"},"products":["bambuddy"],"published":"2026-02-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-06","vendors":["maziggy"]},"summary":"Attackers can bypass authentication and access sensitive data due to hardcoded JWT keys and missing auth checks in Bambuddy.","url":"https://insights.sbomify.com/CVE-2026-25505/"}