Openclaw cli: OpenClaw has incomplete Fix for CVE-2026-27486: Unvalidated SIGKILL in `!stop` Chat Command via
Affects openclaw-cliSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.1 Medium : upgrade to 2026.3.24 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.3.24
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 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.3.24.
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 CLI version 2026.3.24. Users should upgrade to this version or later to ensure the `!stop` command uses the patched killProcessTree function that implements a graceful shutdown sequence. No additional mitigation is required once the update is applied.
Description
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.3.24 contain an incomplete fix for CVE-2026-27486. The `!stop` chat command uses an unpatched function that immediately sends SIGKILL to background bash processes without first sending SIGTERM, preventing graceful shutdown. This behavior was intended to be fixed by introducing a graceful shutdown sequence that sends SIGTERM first and only escalates to SIGKILL after a grace period. The incomplete fix leaves a copy of the vulnerable kill function in the codebase, which is still used by the `!stop` command. A patch is available in OpenClaw 2026.3.24 that addresses this issue.