AI agent vulnerability · OpenClaw

CVE-2026-28464: OpenClaw has non-constant-time token comparison in hooks authentication

highCVSS 4.0 8.2 · 3.1 5.9GHSA-jmm5-fvh5-gf4p

Summary OpenClaw hooks previously compared the provided hook token using a regular string comparison. Because this comparison is not constant-time, an attacker with network access to the hooks endpoint could potentially use timing measurements across many requests to gradually infer the token. In practice, this typically requires hooks to be exposed to an untrusted network and a large number of requests;

Published Mar 2, 2026 · Updated Mar 6, 2026

Affected packages

openclaw

Ecosystem: npm
Affected: < 2026.2.12
Fixed in: 2026.2.12
Check: npm ls openclaw

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

OpenClaw hooks previously compared the provided hook token using a regular string comparison. Because this comparison is not constant-time, an attacker with network access to the hooks endpoint could potentially use timing measurements across many requests to gradually infer the token.

In practice, this typically requires hooks to be exposed to an untrusted network and a large number of requests; real-world latency and jitter can make reliable measurement difficult.

Affected Packages / Versions

openclaw (npm): < 2026.2.12

Patched Versions

openclaw (npm): >= 2026.2.12

Mitigations

Upgrade to openclaw >= 2026.2.12.
If users cannot upgrade immediately: restrict network access to the hooks endpoint and rotate the hooks token after updating.

Fix Commit(s)

113ebfd6a23c4beb8a575d48f7482593254506ec

OpenClaw thanks @akhmittra for reporting.

Credited to akhmittra.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries