Grav before 2.0.14 fails to guard the access field in the core group blueprint with the required security@: admin.super restriction. A delegated admin.users operator can save a group with access[admin][super]=true to escalate to super-admin, gaining scheduler and Twig evaluation capabilities.
CVE-2026-75837
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-18. a secondary CVSS source baseline 9.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(high)
- EG Risk
- 57(Track*)EG Risk 57/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 computedSeverity91% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 18, 2026Grav before 2.0.14 Privilege Escalation via Group Access Field | Advisories | VulnCheck
https://www.vulncheck.com/advisories/grav-before-privilege-escalation-via-group-access-fieldMissing admin.super guard on core group blueprint access field allows admin.users operator to escalate to super-admin · Advisory · getgrav/grav · GitHub
https://github.com/getgrav/grav/security/advisories/GHSA-xhfv-7758-r9hxVendor Advisories for CVE-2026-75837(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 26× in last 7d / 26× 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.
- 2026-08-21 07:24 UTCGHSA enrichment
- 2026-08-21 03:03 UTCEG score recompute
- 2026-08-21 03:03 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 22:42 UTCGHSA enrichment
- 2026-08-20 18:22 UTCGHSA enrichment
- 2026-08-20 14:01 UTCGHSA enrichment
- 2026-08-20 08:52 UTCGHSA enrichment
- 2026-08-20 04:32 UTCGHSA enrichment
- 2026-08-20 00:10 UTCGHSA enrichment
- 2026-08-19 19:47 UTCEG score recompute
- 2026-08-19 19:47 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:25 UTCEG score recompute
- 2026-08-19 15:25 UTCGHSA enrichment
- 2026-08-19 14:38 UTCEG score recompute
- 2026-08-19 14:38 UTCGHSA enrichment
- 2026-08-19 10:40 UTCGHSA enrichment
- 2026-08-19 06:19 UTCGHSA enrichment
- 2026-08-19 01:57 UTCGHSA enrichment
- 2026-08-18 21:36 UTCGHSA enrichment
- 2026-08-18 16:58 UTCGHSA enrichment
- 2026-08-18 12:34 UTCEG score recompute
- 2026-08-18 12:34 UTCGHSA enrichment
- 2026-08-18 11:29 UTCEG score recompute
Show 1 moreShow fewer
- 2026-08-18 11:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(5)
What is CVE-2026-75837?
When was CVE-2026-75837 disclosed?
Is CVE-2026-75837 actively exploited?
What is the CVSS score of CVE-2026-75837?
How do I remediate CVE-2026-75837?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75837
Is Your Infrastructure Affected by CVE-2026-75837?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.