Quick answers
- Is CVE-2026-72561 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72561 being exploited in the wild.
- How severe is CVE-2026-72561?
- High severity, with a CVSS score of 8.8, published 11 August 2026.
- Which products and versions are affected?
- Peppermint Lab Peppermint through commit ba6e217.
- Is there a fix for CVE-2026-72561?
- 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-72561 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-72561?
- 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
This is a broken access control vulnerability (CWE-639) in Peppermint's OIDC/SSO configuration endpoint. The endpoint fails to perform role-based authorization checks before processing requests to modify global OIDC issuer settings. Any authenticated user can send a request to reconfigure the OIDC issuer URL, bypassing the administrative role requirement. An attacker needs only a valid user account on the platform (no special privileges required). The vulnerability allows credential harvesting by redirecting SSO logins to an attacker-controlled identity provider, potentially compromising all platform users. The affected code is in commit ba6e217 and earlier versions.
Affected products
- Peppermint Lab Peppermint through commit ba6e217
Timeline
- 2026-08-11: disclosed
- 2026-07-17: other: Repository archived by owner on July 17, 2026