How severe is GHSA-jccr-rrw2-vc8h?

GHSA-jccr-rrw2-vc8h has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jccr-rrw2-vc8h?

GHSA-jccr-rrw2-vc8h affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-jccr-rrw2-vc8h?

Update openclaw to 2026.3.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jccr-rrw2-vc8h is resolved across your whole dependency graph.

How do I detect GHSA-jccr-rrw2-vc8h in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-jccr-rrw2-vc8h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-jccr-rrw2-vc8h?

O3 pinpoints whether GHSA-jccr-rrw2-vc8h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jccr-rrw2-vc8h actively exploited in the wild?

No public exploit code has been indexed for GHSA-jccr-rrw2-vc8h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-jccr-rrw2-vc8h published, and has it been updated?

GHSA-jccr-rrw2-vc8h was published on March 31, 2026 and was last updated on April 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-jccr-rrw2-vc8h

HIGH

OpenClaw safeBins jq `$ENV` filter bypass allows environment variable disclosure

Published

Mar 31, 2026

Updated

Apr 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / week

Description

Summary

The jq safe-bin policy blocked explicit env usage but still allowed jq programs that accessed environment data through $ENV.

Impact

An operator-approved safe-bin jq command could disclose environment variables that the safe-bin policy was supposed to keep out of scope.

Affected Component

src/infra/exec-safe-bin-semantics.ts

Fixed Versions

Affected: <= 2026.3.24
Patched: >= 2026.3.28
Latest stable 2026.3.28 contains the fix.

Fix

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.3.28

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.3.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jccr-rrw2-vc8h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jccr-rrw2-vc8h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jccr-rrw2-vc8h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary The jq safe-bin policy blocked explicit `env` usage but still allowed jq programs that accessed environment data through `$ENV`. ## Impact An operator-approved safe-bin jq command could disclose environment variables that the safe-bin policy was supposed to keep out of scope. ## Affected Component `src/infra/exec-safe-bin-semantics.ts` ## Fixed Versions - Affected: `<= 2026.3.24` - Patched: `>= 2026.3.28` - Latest stable `2026.3.28` contains the fix. ## Fix Fixed by commit `78e2f3d66d` (`Exec: tighten jq safe-bin env checks`). Thanks @nicky-cc of Tencent zhuque Lab ([http

O3 Security · Impact-Aware SCA

Is GHSA-jccr-rrw2-vc8h in your dependencies?

O3 detects GHSA-jccr-rrw2-vc8h across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works