https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-09-30T14:49:13.482928+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-28464 BREW-openclaw-cli-CVE-2026-28464 — OpenClaw has non-constant-time token comparison in hooks authentication 2026-09-30T14:49:13.484117+00:00

Affected: Homebrew: openclaw-cli

## 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.

 https://db.gcve.eu/vuln/cve-2026-28464 CVE-2026-28464 — OpenClaw < 2026.2.12 - Timing Attack in Hooks Token Authentication 2026-09-30T14:49:13.484197+00:00

Affected: OpenClaw

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.