Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-jfv4-h8mc-jcp8
No affected components available
Summary
OpenClaw CLI process cleanup used system-wide process enumeration and pattern matching to terminate processes without verifying they were owned by the current OpenClaw process. On shared hosts, unrelated processes could be terminated if they matched the pattern.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
< 2026.2.14(including the latest published version2026.2.13) - Fixed:
2026.2.14(planned next release)
Details
The CLI runner cleanup helpers could kill processes matched by command-line patterns without validating process ownership.
Fix
Process cleanup is now scoped to owned processes only by filtering to direct child PIDs of the current process (ppid == process.pid) before sending signals.
Hardening follow-ups:
- Prefer graceful termination for resume cleanup (
SIGTERM, thenSIGKILLfallback). - Reduce false negatives from
psargv truncation by preferring wide output (ps -axww) with a fallback. - Tighten command-line token matching to avoid substring matches.
Fix Commit(s)
- 6084d13b956119e3cf95daaf9a1cae1670ea3557
- eb60e2e1b213740c3c587a7ba4dbf10da620ca66
Release Process Note
This advisory is pre-set with patched version 2026.2.14. After 2026.2.14 is published to npm, the remaining step should be to publish this advisory.
Thanks @aether-ai-agent for reporting.
The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability.
Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard