CVE-2026-72561

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A broken access control vulnerability in Peppermint Lab Peppermint through commit ba6e217 allows any authenticated non-administrative user to reconfigure the platform global OIDC/SSO settings via an unprotected configuration endpoint. The endpoint performs no administrative role check before applying new OIDC issuer settings. An attacker can redirect all SSO logins to an attacker-controlled identity provider, enabling credential harvesting for all platform users.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

GitHub - Peppermint-Lab/peppermint: An open source issue management & help desk solution. A zendesk & jira alternative · GitHub

https://github.com/Peppermint-Lab/peppermint

Vendor Advisories for CVE-2026-72561(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 03:56 UTCEG score recompute
  2. 2026-08-21 03:56 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 15:08 UTCGHSA enrichment
  5. 2026-08-20 02:20 UTCEG score recompute
  6. 2026-08-20 02:20 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 13:31 UTCGHSA enrichment
  9. 2026-08-19 00:43 UTCEG score recompute
  10. 2026-08-19 00:43 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 11:55 UTCGHSA enrichment
  14. 2026-08-17 23:07 UTCEG score recompute
  15. 2026-08-17 23:07 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 10:15 UTCGHSA enrichment
  18. 2026-08-16 21:28 UTCEG score recompute
  19. 2026-08-16 21:28 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 08:40 UTCEG score recompute
  23. 2026-08-16 08:40 UTCGHSA enrichment
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 19:52 UTCGHSA enrichment
Show 18 more
  1. 2026-08-15 07:04 UTCEG score recompute
  2. 2026-08-15 07:04 UTCGHSA enrichment
  3. 2026-08-15 01:31 UTCEPSS rescore
  4. 2026-08-14 18:15 UTCGHSA enrichment
  5. 2026-08-14 05:27 UTCEG score recompute
  6. 2026-08-14 05:27 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 16:39 UTCGHSA enrichment
  9. 2026-08-13 03:50 UTCGHSA enrichment
  10. 2026-08-12 15:02 UTCEG score recompute
  11. 2026-08-12 15:02 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-12 02:14 UTCGHSA enrichment
  14. 2026-08-11 13:25 UTCEG score recompute
  15. 2026-08-11 13:25 UTCGHSA enrichment
  16. 2026-08-11 12:26 UTCEG score recompute
  17. 2026-08-11 11:22 UTCEG score recompute
  18. 2026-08-11 11:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72561?
CVE-2026-72561 is a high vulnerability published on August 11, 2026. A broken access control vulnerability in Peppermint Lab Peppermint through commit ba6e217 allows any authenticated non-administrative user to reconfigure the platform global OIDC/SSO settings via an unprotected configuration endpoint. The endpoint performs no administrative role check before…
When was CVE-2026-72561 disclosed?
CVE-2026-72561 was first published in the National Vulnerability Database on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72561 actively exploited?
CVE-2026-72561 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.7% of all scored CVEs.
What is the CVSS score of CVE-2026-72561?
CVE-2026-72561 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-72561?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72561, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72561

Explore →

Is Your Infrastructure Affected by CVE-2026-72561?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.