Summary
The jq safe-bin policy blocked explicit env usage but still allowed jq programs that accessed environment data through $ENV.
Affected Component
src/infra/exec-safe-bin-semantics.ts
Fixed Versions
- Affected:
<= 2026.3.24 - Patched:
>= 2026.3.28 - Latest stable
2026.3.28contains the fix.
Impact
An operator-approved safe-bin jq command could disclose environment variables that the safe-bin policy was supposed to keep out of scope.
GHSA-JCCR-RRW2-VC8H has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.3.28); upgrading removes the vulnerable code path.
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.
Remediation advice
Fixed by commit 78e2f3d66d (Exec: tighten jq safe-bin env checks).
Thanks @nicky-cc of Tencent zhuque Lab (https://github.com/Tencent/AI-Infra-Guard) for reporting.
Frequently Asked Questions
- What is GHSA-JCCR-RRW2-VC8H? GHSA-JCCR-RRW2-VC8H is a high-severity security vulnerability in openclaw (npm), affecting versions <= 2026.3.24. It is fixed in 2026.3.28.
- How severe is GHSA-JCCR-RRW2-VC8H? GHSA-JCCR-RRW2-VC8H has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of openclaw are affected by GHSA-JCCR-RRW2-VC8H? openclaw (npm) versions <= 2026.3.24 is affected.
- Is there a fix for GHSA-JCCR-RRW2-VC8H? Yes. GHSA-JCCR-RRW2-VC8H is fixed in 2026.3.28. Upgrade to this version or later.
- Is GHSA-JCCR-RRW2-VC8H exploitable, and should I be worried? Whether GHSA-JCCR-RRW2-VC8H 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-JCCR-RRW2-VC8H 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-JCCR-RRW2-VC8H? Upgrade
openclawto 2026.3.28 or later.