OpenClaw: Config writes could persist resolved ${VAR} secrets to disk
## 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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-28475US | low3.7 | — | ||
OpenClaw versions prior to 2026.2.13 use non-constant-time string comparison for hook token validation, allowing attackers to infer tokens through timing measurements. Remote attac… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/openclaw/openclawPACKAGE
- https://github.com/openclaw/openclaw/commit/113ebfd6a23c4beb8a575d48f7482593254506ecWEB
- https://github.com/openclaw/openclaw/security/advisories/GHSA-47q7-97xp-m272WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-28475ADVISORY
- https://www.vulncheck.com/advisories/openclaw-timing-attack-via-hook-token-comparisonWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan