# CVE-2026-85392: Peppermint through 0.5.5 Authorization Bypass on the User Logout Endpoint

> Authenticated attackers can forcibly log out any user, including administrators, by exploiting missing authorization checks on the logout endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/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:** No
- **Published:** 3 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-r5f6-fc86-75rh

## What is CVE-2026-85392?

CVE-2026-85392 is a medium-severity missing authorization vulnerability in Peppermint-Lab peppermint, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Peppermint through 0.5.5 contains an authorization bypass vulnerability in the GET /api/v1/auth/user/:id/logout endpoint that allows authenticated attackers to delete sessions for any user by supplying arbitrary user IDs. Attackers can forcibly log out any user including administrators by calling the logout handler with another user's ID, since the endpoint performs no authorization checks to verify the caller owns the target account.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-85392 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85392 is a medium-severity missing authorization vulnerability in Peppermint-Lab peppermint, published on 3 Sep 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-85392 in the wild and no public exploit code.

Affected product: Peppermint-Lab 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-85392/ (Markdown: https://insights.sbomify.com/CVE-2026-85392/index.md)
```

## Sources

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

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