CVE-2026-72701

LOWPre-NVD 3.73.7—
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory published 2026-08-25. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: Elevated riskExposed: 0

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

Grav CMS before 2.0.16 contains a timing vulnerability in Utils::verifyNonce() that uses non-constant-time string comparison with the === operator instead of hash_equals() for CSRF nonce validation. Attackers can measure response timing differences to recover valid nonce values byte-by-byte through multiple requests, weakening CSRF protection below its intended security margin.

CVSS v3
3.7
EG Score
3.7(high)
EG Risk
33(Track)
EG Risk 33/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
Severity37% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 31, 2026

References (3)

Vendor Advisories for CVE-2026-72701(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 9× in last 7d / 38× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-16 15:42 UTCEG score recompute
  3. 2026-09-16 15:42 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-13 11:43 UTCEG score recompute
  8. 2026-09-13 11:43 UTCGHSA enrichment
  9. 2026-09-12 15:02 UTCEPSS rescore
  10. 2026-09-10 09:35 UTCEPSS rescore
  11. 2026-09-10 08:01 UTCEG score recompute
  12. 2026-09-10 08:01 UTCGHSA enrichment
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-07 04:19 UTCEG score recompute
  15. 2026-09-07 04:19 UTCGHSA enrichment
  16. 2026-09-06 13:48 UTCEPSS rescore
  17. 2026-09-04 05:07 UTCEPSS rescore
  18. 2026-09-04 00:37 UTCEG score recompute
  19. 2026-09-04 00:37 UTCGHSA enrichment
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 13:54 UTCEPSS rescore
  22. 2026-08-31 20:55 UTCGHSA enrichment
  23. 2026-08-30 21:18 UTCEG score recompute
  24. 2026-08-30 21:18 UTCGHSA enrichment
  25. 2026-08-30 19:18 UTCEPSS rescore
Show 13 more
  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 17:37 UTCEG score recompute
  5. 2026-08-27 17:37 UTCGHSA enrichment
  6. 2026-08-27 17:14 UTCEG score recompute
  7. 2026-08-27 17:14 UTCGHSA enrichment
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 14:47 UTCEPSS rescore
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-25 02:19 UTCEG score recompute
  12. 2026-08-25 01:50 UTCEG score recompute
  13. 2026-08-25 01:50 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72701?
CVE-2026-72701 is a low vulnerability published on August 25, 2026. Grav CMS before 2.0.16 contains a timing vulnerability in Utils::verifyNonce() that uses non-constant-time string comparison with the === operator instead of hash_equals() for CSRF nonce validation. Attackers can measure response timing differences to recover valid nonce values byte-by-byte through…
When was CVE-2026-72701 disclosed?
CVE-2026-72701 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72701 actively exploited?
CVE-2026-72701 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 92.3% of all scored CVEs.
What is the CVSS score of CVE-2026-72701?
CVE-2026-72701 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-72701?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72701, 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-72701

Explore →

Is Your Infrastructure Affected by CVE-2026-72701?

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

Start Free Scan →Browse All CVEs