CVE-2026-34970

CVE-2026-34970 is a medium-severity security vulnerability in mantisbt/mantisbt (composer), affecting versions <= 2.28.1. It is fixed in 2.28.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

MantisBT: Bugnote Revision Page Leaks Private Issue Metadata After Issue Access Is Revoked

MantisBT allows a bugnote author to access the note's Revisions page after losing access to the parent private issue.

Workarounds

None

Credits

Thanks to Vishal Shukla for discovering and responsibly reporting the issue.

Impact

Disclosure of the private Issue's Id and Summary. The bugnote full revision body remains secure.

Affected versions

mantisbt/mantisbt (<= 2.28.1)

Security releases

mantisbt/mantisbt → 2.28.2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

  • 71df1f67e05b2050cd4bd87839e6cc13747cf03f

Frequently Asked Questions

  1. What is CVE-2026-34970? CVE-2026-34970 is a medium-severity security vulnerability in mantisbt/mantisbt (composer), affecting versions <= 2.28.1. It is fixed in 2.28.2.
  2. Which versions of mantisbt/mantisbt are affected by CVE-2026-34970? mantisbt/mantisbt (composer) versions <= 2.28.1 is affected.
  3. Is there a fix for CVE-2026-34970? Yes. CVE-2026-34970 is fixed in 2.28.2. Upgrade to this version or later.
  4. Is CVE-2026-34970 exploitable, and should I be worried? Whether CVE-2026-34970 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-34970 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-34970? Upgrade mantisbt/mantisbt to 2.28.2 or later.

Other vulnerabilities in mantisbt/mantisbt

Stop the waste.
Protect your environment with Kodem.