Summary
OpenClaw: Sandbox file operations use check-then-act, bypassing fd-based TOCTOU defenses
Sandbox file operations use check-then-act, bypassing fd-based TOCTOU defenses
Current Maintainer Triage
- Status: narrow
- Normalized severity: medium
- Assessment: Released workspace-only apply_patch remove and mkdir operations were still check-then-act, but the draft overstates scope by bundling broader edit paths; keep it open but narrow it to the actual sandbox-workspace mutation boundary.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version:
2026.3.31 - Vulnerable version range:
<=2026.3.28 - Patched versions:
>= 2026.3.31 - First stable tag containing the fix:
v2026.3.31
Fix Commit(s)
32a4a47d602e0618f87b3e59f94d8c142767f860, 2026-03-30T16:49:49+01:00
OpenClaw thanks @AntAISecurityLab for reporting.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-RM5C-4RMF-VVHW? GHSA-RM5C-4RMF-VVHW is a medium-severity security vulnerability in openclaw (npm), affecting versions <= 2026.3.28. It is fixed in 2026.3.31.
- Which versions of openclaw are affected by GHSA-RM5C-4RMF-VVHW? openclaw (npm) versions <= 2026.3.28 is affected.
- Is there a fix for GHSA-RM5C-4RMF-VVHW? Yes. GHSA-RM5C-4RMF-VVHW is fixed in 2026.3.31. Upgrade to this version or later.
- Is GHSA-RM5C-4RMF-VVHW exploitable, and should I be worried? Whether GHSA-RM5C-4RMF-VVHW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-RM5C-4RMF-VVHW is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-RM5C-4RMF-VVHW? Upgrade
openclawto 2026.3.31 or later.