Summary
OpenClaw: Feishu docx uploadfile/uploadimage Bypasses Workspace-Only Filesystem Policy (GHSA-qf48-qfv4-jjm9 Incomplete Fix)
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<=2026.4.3 - Patched versions:
2026.4.8
Verification
The fix was re-checked against main before publication, including targeted regression tests for the affected security boundary.
Credits
Thanks @Rosayxy for reporting.
Impact
Feishu docx upload_file/upload_image Bypasses Workspace-Only Filesystem Policy (GHSA-qf48-qfv4-jjm9 Incomplete Fix).
Feishu document uploads could read local files outside the workspace-only file policy when processing docx upload blocks.
OpenClaw is a user-controlled local assistant. This advisory is scoped to the OpenClaw trust model and does not assume a multi-tenant service boundary.
A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.
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 on main and is available in the patched npm version listed above. The verified fixed tree is commit d7c3210cd6f5fdfdc1beff4c9541673e814354d5.
Frequently Asked Questions
- What is CVE-2026-41911? CVE-2026-41911 is a low-severity incorrect permission assignment for critical resource vulnerability in openclaw (npm), affecting versions < 2026.4.8. It is fixed in 2026.4.8. A file, directory, or other resource is assigned permissions that allow broader access than intended.
- Which versions of openclaw are affected by CVE-2026-41911? openclaw (npm) versions < 2026.4.8 is affected.
- Is there a fix for CVE-2026-41911? Yes. CVE-2026-41911 is fixed in 2026.4.8. Upgrade to this version or later.
- Is CVE-2026-41911 exploitable, and should I be worried? Whether CVE-2026-41911 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-41911 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-41911? Upgrade
openclawto 2026.4.8 or later.