Sandbox cache poisoning via colliding configuration hashes
Published Mar 5, 2026 · Updated Mar 5, 2026
Cache poisoning in OpenClaw before 2026.2.15 allows remote attackers to reuse unsafe sandbox state through colliding configuration cache keys. The computeHash function serializes normalized Docker and browser sandbox configurations and uses collision-prone SHA-1 output as their deterministic cache identity. Exploitation requires a chosen collision across configuration payloads; matching identities can suppress required sandbox recreation and reuse state intended for another configuration.
Summary
What happened
Cache poisoning in OpenClaw before 2026.2.15 allows remote attackers to reuse unsafe sandbox state through colliding configuration cache keys. The computeHash function serializes normalized Docker and browser sandbox configurations and uses collision-prone SHA-1 output as their deterministic cache identity. Exploitation requires a chosen collision across configuration payloads; matching identities can suppress required sandbox recreation and reuse state intended for another configuration.
The record
- CVE
- CVE-2026-28479
- Published
- Mar 5, 2026
- Updated
- Mar 5, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2026CVE publishedPublication date reported by the CVE source.
- Mar 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.2.15
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo