Skip to main content
VulnerabilityPublished Updated

CVE-2026-32977: OpenClaw · Sandbox `writeFile` commit could race outside the validated path

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2026.3.11 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

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

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 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.11.

Affected software

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

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

AI-suggested

Upgrade openclaw-cli to version 2026.3.11 or later, where the vulnerability is fixed by anchoring the writeFile commit path to prevent the race condition. No other workarounds are indicated.

Description

A race condition vulnerability in openclaw-cli's sandbox file system bridge writeFile commit step allows an attacker to bypass sandbox boundaries by redirecting file writes outside the validated sandbox path. This affects versions prior to 2026.3.11 and is fixed in that version.

References

Community reviews

Loading reviews…