Summary
OpenClaw: screen_record outPath bypassed workspace-only filesystem guard
screen_record outPath bypassed workspace-only filesystem guard.
Affected Packages / Versions
- Package:
openclaw - Ecosystem: npm
- Affected versions:
< 2026.4.10 - Patched versions:
>= 2026.4.10
Technical Details
The fix applies the workspace-root guard to node tool outPath handling, including screen recording paths.
Fix Commit(s)
635bb35b68d8faa5bfa2fda35feadd315122748a- PR: #63551
Release Process Note
Users should upgrade to openclaw 2026.4.10 or newer. The latest npm release, 2026.4.14, already includes the fix.
Credits
Thanks to @anshumanbh for reporting this issue.
Impact
The node-host screen recording tool could honor an outPath outside the workspace guard, allowing an authorized tool call to write outside the intended workspace boundary.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
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
The issue was fixed in #63551. The first stable tag containing the fix is v2026.4.10, and [email protected] includes the fix.
Frequently Asked Questions
- What is CVE-2026-43567? CVE-2026-43567 is a medium-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.4.10. It is fixed in 2026.4.10. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of openclaw are affected by CVE-2026-43567? openclaw (npm) versions < 2026.4.10 is affected.
- Is there a fix for CVE-2026-43567? Yes. CVE-2026-43567 is fixed in 2026.4.10. Upgrade to this version or later.
- Is CVE-2026-43567 exploitable, and should I be worried? Whether CVE-2026-43567 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 CVE-2026-43567 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 CVE-2026-43567? Upgrade
openclawto 2026.4.10 or later.