Quick answers
- Is CVE-2026-72555 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72555 being exploited in the wild.
- How severe is CVE-2026-72555?
- High severity, with a CVSS score of 8.1, published 11 August 2026.
- Which products and versions are affected?
- Peppermint Lab Peppermint through commit ba6e217.
- Is there a fix for CVE-2026-72555?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-72555 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-72555?
- Check whether you run Peppermint Lab Peppermint 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.
Technical details
The vulnerability is a broken access control issue in Peppermint's permission checking logic. The root cause is that the Config.roles_active flag defaults to false, causing all permission checks on ticket, client, and user handlers to behave as no-ops (perform no validation). An authenticated attacker can bypass ownership and administrative access controls by default, gaining the ability to read, modify, or delete any ticket, client, or user record regardless of ownership. The vulnerability affects all default installations through commit ba6e217. No patch status is explicitly documented in the advisory.
Affected products
- Peppermint Lab Peppermint through commit ba6e217
Timeline
- 2026-08-11: disclosed