# CVE-2026-72555: Peppermint Lab Peppermint - Broken Access Control

> Authenticated users can read, modify, or delete tickets, clients, and users belonging to other accounts due to default permission checks being disabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-jv42-7r5q-7p5r

## What is CVE-2026-72555?

CVE-2026-72555 is a high-severity missing authorization vulnerability in Peppermint, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A broken access control vulnerability in Peppermint Lab Peppermint through commit ba6e217 exists because the Config.roles_active flag defaults to false, causing all permission checks on ticket, client, and user handlers to behave as no-ops on default installations. All authenticated users bypass ownership and administrative access controls. An attacker with any user account can read, modify, or delete tickets, clients, and users belonging to any other account.

Weakness: CWE-284 (Improper Access Control)

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


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

No fix has been published for CVE-2026-72555 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72555 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72555 is a high-severity missing authorization vulnerability in Peppermint, published on 11 Aug 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-72555 in the wild and no public exploit code.

Affected product: Peppermint. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-72555/ (Markdown: https://insights.sbomify.com/CVE-2026-72555/index.md)
```

## Sources

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

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