{"answers":{"affected":"2 open source packages ship an affected version, including mantisbt/mantisbt.","exploited":"There is no known exploitation of CVE-2026-42071 in the wild and no public exploit code.","fix":"Upgrade mantisbt/mantisbt to 2.28.2 or later.","what":"CVE-2026-42071 is a high-severity missing authorization vulnerability in mantisbt, published on 28 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-42071 and fix it if it is affected.\n\nWhat it is: CVE-2026-42071 is a high-severity missing authorization vulnerability in mantisbt, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-42071 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mantisbt/mantisbt (Packagist): affected from 2.23.0; fixed in 2.28.2\n- mantisbt/mantisbt (Packagist): affected from 2.23.0; 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-42071/ (Markdown: https://insights.sbomify.com/CVE-2026-42071/index.md)","id":"CVE-2026-42071","markdown":"https://insights.sbomify.com/CVE-2026-42071/index.md","name":"CVE-2026-42071","record":{"aliases":["GHSA-pw5x-2mf9-3xc8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Issue tracker","requires_auth":"low_privilege","summary":"Authenticated users can download private bugnote attachments via API endpoints due to missing authorization checks in MantisBT.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Mantis Bug Tracker (MantisBT) is an open source issue tracker. From 2.23.0 to 2.28.1, a missing authorization check in MantisBT's file visibility function allows any authenticated user (REPORTER+) to download attachments on private bugnotes they should not be able to access, via the REST API endpoint GET /api/rest/issues/{id}/files and SOAP API mc_issue_attachment_get endpoint. This vulnerability is fixed in 2.28.2.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"MantisBT: Private Bugnote Attachment Content Leak via REST API","id":"CVE-2026-42071","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Nornicdb: Improper Network Binding in NornicDB Bolt Server allows unauthorized remote access","id":"CVE-2026-42072"},"packages":[{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["2.23.0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":null,"source":"GHSA-pw5x-2mf9-3xc8"},{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["2.23.0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":"pkg:composer/mantisbt/mantisbt","source":"GHSA-pw5x-2mf9-3xc8"}],"prev":{"headline":"MantisBT: Authorization Bypass in Bugnote Editing via Issue Update API","id":"CVE-2026-42070"},"products":["mantisbt"],"published":"2026-05-28","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-29","vendors":["mantisbt"]},"summary":"Authenticated users can download private bugnote attachments via API endpoints due to missing authorization checks in MantisBT.","url":"https://insights.sbomify.com/CVE-2026-42071/"}