# CVE-2026-34744: MantisBT authorization bypass allows continued access to self-uploaded attachments on private issues

> Users can access their own attachments on private issues created by others, bypassing read access restrictions in MantisBT.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-rmp5-5jj7-gmvf

## What is CVE-2026-34744?

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.

### Official 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.

Weakness: CWE-281 (Improper Preservation of Permissions), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-34744?

2 open source packages ship an affected version, including mantisbt/mantisbt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mantisbt/mantisbt` | Packagist | All versions | 2.28.2 |
| `mantisbt/mantisbt` | Packagist | All versions | 2.28.2 |

## How do I fix CVE-2026-34744?

Upgrade mantisbt/mantisbt to 2.28.2 or later.

## Is CVE-2026-34744 being exploited?

There is no known exploitation of CVE-2026-34744 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34744 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-34744 in the wild and no public exploit code.

Affected packages and fixed versions:
- mantisbt/mantisbt (Packagist): affected all versions; fixed in 2.28.2
- mantisbt/mantisbt (Packagist): affected all versions; fixed in 2.28.2

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34744/ (Markdown: https://insights.sbomify.com/CVE-2026-34744/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34744
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34744
- OSV: https://osv.dev/vulnerability/CVE-2026-34744

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34744/
Summaries are generated and may contain mistakes; the official description above is the record.