OpenClaw versions prior to 2026.2.12 use non-constant-time string comparison for hook token validation, allowing attackers to infer tokens through timing measurements. Remote attackers with network access to the hooks endpoint can exploit timing side-channels across multiple requests to gradually determine the authentication token.
CVE-2026-28464
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
March 5, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 2, 2026OpenClaw < 2026.2.12 - Timing Attack in Hooks Token Authentication | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openclaw-timing-attack-in-hooks-token-authenticationNon-constant-time token comparison in hooks authentication · Advisory · openclaw/openclaw · GitHub
https://github.com/openclaw/openclaw/security/advisories/GHSA-jmm5-fvh5-gf4pcommit 113ebfd6a23c (openclaw/openclaw)
Fix landed in openclaw/openclaw commit 113ebfd6a23c — awaiting tagged release
https://github.com/openclaw/openclaw/commit/113ebfd6a23c4beb8a575d48f7482593254506ecAffected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openclaw | — | 2026.2.12 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 30× 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-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 23:59 UTCOSV refresh
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
Show 38 moreShow fewer
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:24 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 08:20 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 23:55 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 22:39 UTCEG score recompute
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 05:28 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 19:59 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 07:59 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 19:36 UTCEG score recompute
- 2026-08-06 20:53 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 02:28 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 01:59 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 18:41 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:50 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-28464?
When was CVE-2026-28464 disclosed?
Is CVE-2026-28464 actively exploited?
What is the CVSS score of CVE-2026-28464?
How do I remediate CVE-2026-28464?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-28464
Is Your Infrastructure Affected by CVE-2026-28464?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.