Skip to main content
VulnerabilityPublished Updated

CVE-2026-28479: Openclaw cli · OpenClaw replaced a deprecated sandbox hash algorithm

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2026.2.15 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.2.15
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.2.15.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.2.15
Fixed in
  • 2026.2.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in openclaw version 2026.2.15 that replaces SHA-1 with SHA-256 for sandbox cache key hashing. Users should upgrade to version 2026.2.15 or later to mitigate this vulnerability.

Description

OpenClaw CLI versions up to 2026.2.14 used the deprecated SHA-1 hashing algorithm for sandbox identifier cache keys. This hashing was used to determine if existing sandbox containers could be safely reused. Because SHA-1 is vulnerable to collisions, this posed a risk of cache poisoning and unsafe sandbox state reuse. The vulnerability is fixed in version 2026.2.15 by replacing SHA-1 with SHA-256 for these hashes, restoring collision resistance.

References

Community reviews

Loading reviews…