Quick answers
- Is CVE-2026-34744 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34744 being exploited in the wild.
- How severe is CVE-2026-34744?
- Medium severity, with a CVSS score of 4, published 19 May 2026.
- Which products and versions are affected?
- MantisBT Mantis Bug Tracker <= 2.28.1; MantisBT <= 2.28.1; mantisbt/mantisbt (Packagist) <= 2.28.1, ECOSYSTEM:introduced=0,fixed=2.28.2.
- Is there a fix for CVE-2026-34744?
- Yes. mantisbt/mantisbt (Packagist): upgrade to 2.28.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34744 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-34744?
- Check whether you run MantisBT Mantis Bug Tracker, MantisBT or mantisbt/mantisbt (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- mantisbt/mantisbt (Packagist): upgrade to 2.28.2 or later
composer require mantisbt/mantisbt:^2.28.2
Technical details
An authorization bypass vulnerability exists in MantisBT (versions up to 2.28.1) due to improper access control checks on attachments. Specifically, the system fails to revoke access to attachments for the original uploader when the parent issue's visibility is changed to 'private' or when the user's permissions to the issue are otherwise removed. An authenticated attacker with network access can exploit this to list and download files they previously attached to an issue they can no longer view. The vulnerability is addressed in version 2.28.2.
Affected products
- MantisBT MantisBT <= 2.28.1
Identifiers
- CVE-2026-34744
- GHSA-rmp5-5jj7-gmvf
Timeline
- 2026-05-09: disclosed: Initial disclosure by researcher
- 2026-05-11: advisory: GitHub Advisory published
- 2026-05-19: other: NVD published date