CVE-2026-100670

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-26. 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 weekElevated
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.3%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Grav CMS 2.0.14 through 2.0.24 contains a privilege escalation vulnerability in the group and account blueprints. The access map is gated by a security@: admin.super guard that is resolved by the field's exact path, so a submitted flat dot-notation key such as access.admin.super (instead of the nested access[admin][super]) matches no blueprint rule, survives BlueprintSchema::filterArray() and flattening, and is written by FlexObject::update() via setNestedProperty(), which splits on . and reconstructs the nested value. An authenticated backend operator using the flex accounts backend who holds admin.users but not admin.super can therefore grant admin.super to their own account or to a group they belong to and escalate to full super-admin, gaining control over configuration, plugin and theme installation, the file manager, and all accounts. Fixed in 2.0.25, which drops any dotted key whose ancestor path is disabled or marked validate.ignore.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
56
EG Risk 56/100CISA SSVC

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%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Grav CMS 2.0.14 through 2.0.24 Privilege Escalation via Blueprint Guard Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/grav-cms-2.0.14-through-2.0.24-privilege-escalation-via-blueprint-guard-bypass
github Patch Available🟡 PoC Available

Grav CMS group blueprint `security@` guard bypass via flat dot-notation key leads to privilege escalation · Advisory · getgrav/grav · GitHub

https://github.com/getgrav/grav/security/advisories/GHSA-mwjj-r7vm-pgqm

Vendor Advisories for CVE-2026-100670(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 31× in last 7d / 36× 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-10-04 02:54 UTCGHSA enrichment
  2. 2026-10-03 15:00 UTCEG score recompute
  3. 2026-10-03 15:00 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 03:05 UTCEG score recompute
  6. 2026-10-03 03:05 UTCGHSA enrichment
  7. 2026-10-02 15:11 UTCGHSA enrichment
  8. 2026-10-02 03:19 UTCEG score recompute
  9. 2026-10-02 03:19 UTCGHSA enrichment
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 15:25 UTCGHSA enrichment
  12. 2026-10-01 03:32 UTCEG score recompute
  13. 2026-10-01 03:32 UTCGHSA enrichment
  14. 2026-09-30 15:40 UTCEG score recompute
  15. 2026-09-30 15:39 UTCGHSA enrichment
  16. 2026-09-30 15:02 UTCEPSS rescore
  17. 2026-09-30 15:02 UTCEG score recompute
  18. 2026-09-30 15:02 UTCGHSA enrichment
  19. 2026-09-30 13:37 UTCGHSA enrichment
  20. 2026-09-30 01:44 UTCEG score recompute
  21. 2026-09-30 01:44 UTCGHSA enrichment
  22. 2026-09-29 15:20 UTCEPSS rescore
  23. 2026-09-29 13:51 UTCGHSA enrichment
  24. 2026-09-29 01:58 UTCEG score recompute
  25. 2026-09-29 01:58 UTCGHSA enrichment
Show 11 more
  1. 2026-09-28 14:05 UTCEG score recompute
  2. 2026-09-28 14:05 UTCGHSA enrichment
  3. 2026-09-28 13:50 UTCEPSS rescore
  4. 2026-09-28 02:12 UTCGHSA enrichment
  5. 2026-09-27 14:20 UTCEG score recompute
  6. 2026-09-27 14:20 UTCGHSA enrichment
  7. 2026-09-27 02:27 UTCEG score recompute
  8. 2026-09-27 02:27 UTCGHSA enrichment
  9. 2026-09-26 14:33 UTCEG score recompute
  10. 2026-09-26 13:37 UTCEG score recompute
  11. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100670?
CVE-2026-100670 is a high vulnerability published on September 26, 2026. Grav CMS 2.0.14 through 2.0.24 contains a privilege escalation vulnerability in the group and account blueprints. The access map is gated by a security@: admin.super guard that is resolved by the field's exact path, so a submitted flat dot-notation key such as access.admin.super (instead of the…
When was CVE-2026-100670 disclosed?
CVE-2026-100670 was first published on September 26, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100670 actively exploited?
CVE-2026-100670 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100670?
CVE-2026-100670 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100670?
A fix for CVE-2026-100670 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100670 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100670?

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

Book a Demo →Browse All CVEs