Grav before 3.9.1 Timing Attack via Non-Constant-Time Token Comparison (CVE-2026-72700) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-72700

Grav before 3.9.1 Timing Attack via Non-Constant-Time Token Comparison

Answer in brief

CVE-2026-72700 records a Unknown severity vulnerability in Grav before 3.9.1 Timing Attack via Non-Constant-Time Token Comparison. The current sources do not mark it as known exploited. The current feed maps getgrav/grav (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 25, 2026Updated Aug 25, 2026Source checked Aug 25, 2026First seen by HOL Aug 25, 2026Material review Aug 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps getgrav/grav (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
getgrav/gravgeneric	>=0 <3.9.1	3.9.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for getgrav/grav.
Review the reported fix. Update getgrav/grav to 3.9.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 25, 2026

Sources and claim methodology

Upstream source description

The getgrav/grav-plugin-login Composer plugin before 3.9.1 (used by Grav) compares password reset and account activation tokens using a non-constant-time === string comparison instead of hash_equals() in classes/Controller.php (taskReset()) and login.php (activation handler). Because the token-submission endpoint (taskReset) also lacks rate limiting, an attacker could in principle send repeated token guesses against a known username and use the timing differences to attempt to recover a valid token, though the vendor rates the practical exploitability as low and no end-to-end network exploit has been demonstrated.

Quoted source text, attributed separately from HOL analysis.