{"answers":{"affected":"2 open source packages ship an affected version, including mantisbt/mantisbt.","exploited":"There is no known exploitation of CVE-2026-34744 in the wild and no public exploit code.","fix":"Upgrade mantisbt/mantisbt to 2.28.2 or later.","what":"CVE-2026-34744 is a medium-severity missing authorization 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-34744 and fix it if it is affected.\n\nWhat it is: CVE-2026-34744 is a medium-severity missing authorization 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: There is no known exploitation of CVE-2026-34744 in the wild and no public exploit code.\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-34744/ (Markdown: https://insights.sbomify.com/CVE-2026-34744/index.md)","id":"CVE-2026-34744","markdown":"https://insights.sbomify.com/CVE-2026-34744/index.md","name":"CVE-2026-34744","record":{"aliases":["GHSA-rmp5-5jj7-gmvf"],"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":"Users can access their own attachments on private issues created by others, bypassing read access restrictions in MantisBT.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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-281","name":"Improper Preservation of Permissions"},{"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 permit a user to list and download their own attachments from an Issue created by another user even after it becomes private, bypassing read access revocation. The loss of confidentiality caused by this vulnerability is minimal, considering that only attachments previously uploaded by the user themselves remain accessible. This issue has been fixed in version 2.82.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 authorization bypass allows continued access to self-uploaded attachments on private issues","id":"CVE-2026-34744","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Unauthenticated Path Traversal Arbitrary File Write in /api/uploadChunked/public","id":"CVE-2026-34745"},"packages":[{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":null,"source":"GHSA-rmp5-5jj7-gmvf"},{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":"pkg:composer/mantisbt/mantisbt","source":"GHSA-rmp5-5jj7-gmvf"}],"prev":{"headline":"XZ Utils: Buffer overflow in lzma_index_append()","id":"CVE-2026-34743"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-20","vendors":["mantisbt"]},"summary":"Users can access their own attachments on private issues created by others, bypassing read access restrictions in MantisBT.","url":"https://insights.sbomify.com/CVE-2026-34744/"}