Summary
OpenClaw's exec allowlist analysis rejects shell expansion in unquoted heredocs
Exec allowlist analysis rejects shell expansion in unquoted heredocs
Affected Packages / Versions
- Package: openclaw (npm)
- Affected versions: <= 2026.4.21
- Fixed version: 2026.4.22
Fix Commit(s)
- b2e8b7d4bb2f22eaa16f5c4b07547774e90b65a5
Verification
- The fix commit is contained in the public v2026.4.22 tag.
- [email protected] is published on npm and the compiled package contains the fix.
- Focused regression coverage for this path passed before publication.
Thanks @VladimirEliTokarev for reporting.
Impact
An allowlisted command containing an unquoted heredoc could hide shell expansion in the heredoc body. That could make the approved command text look safer than what the shell would evaluate at runtime.
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 exec command analyzer now tracks heredoc bodies, rejects unquoted heredoc expansion tokens and continuation-splice bypasses, and preserves quoted heredocs and literal safe text.
Frequently Asked Questions
- What is GHSA-X3H8-JRGH-P8JX? GHSA-X3H8-JRGH-P8JX is a medium-severity security vulnerability in openclaw (npm), affecting versions <= 2026.4.21. It is fixed in 2026.4.22.
- Which versions of openclaw are affected by GHSA-X3H8-JRGH-P8JX? openclaw (npm) versions <= 2026.4.21 is affected.
- Is there a fix for GHSA-X3H8-JRGH-P8JX? Yes. GHSA-X3H8-JRGH-P8JX is fixed in 2026.4.22. Upgrade to this version or later.
- Is GHSA-X3H8-JRGH-P8JX exploitable, and should I be worried? Whether GHSA-X3H8-JRGH-P8JX 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-X3H8-JRGH-P8JX 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-X3H8-JRGH-P8JX? Upgrade
openclawto 2026.4.22 or later.