{"answers":{"affected":"2 open source packages ship an affected version, including mantisbt/mantisbt.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34970 exists.","fix":"Upgrade mantisbt/mantisbt to 2.28.2 or later.","what":"CVE-2026-34970 is a medium-severity vulnerability in mantisbt, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34970 and fix it if it is affected.\n\nWhat it is: CVE-2026-34970 is a medium-severity vulnerability in mantisbt, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34970 exists.\n\nAffected packages and fixed versions:\n- mantisbt/mantisbt (Packagist): affected all versions; fixed in 2.28.2\n- mantisbt/mantisbt (Packagist): affected all versions; fixed in 2.28.2\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-34970/ (Markdown: https://insights.sbomify.com/CVE-2026-34970/index.md)","id":"CVE-2026-34970","markdown":"https://insights.sbomify.com/CVE-2026-34970/index.md","name":"CVE-2026-34970","record":{"aliases":["GHSA-crmx-4p49-46m2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MantisBT issue tracker","requires_auth":"low_privilege","summary":"Attackers can view private issue metadata via bugnote revision pages even after losing access to the parent issue.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Mantis Bug Tracker (MantisBT) is an open source issue tracker. Versions 2.28.1 and prior allow a bugnote author to access the note's Revisions page after losing access to the parent private issue. This issue has been fixed in version 2.28.2.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"MantisBT Bugnote Revision Page Leaks Private Issue Metadata After Issue Access Is Revoked","id":"CVE-2026-34970","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Wasmtime miscompiled guest heap access enables sandbox escape on aarch64 Cranelift","id":"CVE-2026-34971"},"packages":[{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":null,"source":"GHSA-crmx-4p49-46m2"},{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":"pkg:composer/mantisbt/mantisbt","source":"GHSA-crmx-4p49-46m2"}],"prev":{"headline":"Nhost Leaks the Refresh Token via URL Query Parameter in OAuth Provider Callback","id":"CVE-2026-34969"},"products":["mantisbt"],"published":"2026-05-19","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-20","vendors":["mantisbt"]},"summary":"Attackers can view private issue metadata via bugnote revision pages even after losing access to the parent issue.","url":"https://insights.sbomify.com/CVE-2026-34970/"}