CVE-2026-43529: OpenClaw · TOCTOU read in exec script preflight
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 2.0 Low : upgrade to 2026.4.10 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.07% 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.4.10
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.4.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in OpenClaw version 2026.4.10 and later. Users should upgrade to version 2026.4.10 or newer to eliminate the TOCTOU race condition in the exec script preflight validator. The fix replaces the vulnerable check-then-read flow with an atomic pinned file descriptor open and read, ensuring consistent file identity during validation and reading.
Description
OpenClaw CLI versions prior to 2026.4.10 contain a time-of-check to time-of-use (TOCTOU) race condition in the exec script preflight validator. The validator first validates a script's pathname and then reads the script file by that pathname, allowing an attacker with write access to the workspace path to swap the file between validation and read. This can cause the preflight analysis to inspect a different file than the one originally validated. The impact is limited to derived preflight content exposure and requires local write access to the workspace path. The issue is fixed in version 2026.4.10 by replacing the check-then-read flow with an atomic pinned file descriptor open and read, ensuring the file identity is consistent during validation and reading.