The jq safe-bin policy blocked explicit env usage but still allowed jq programs that accessed environment data through $ENV.
An operator-approved safe-bin jq command could disclose environment variables that the safe-bin policy was supposed to keep out of scope.
src/infra/exec-safe-bin-semantics.ts
<= 2026.3.24>= 2026.3.282026.3.28 contains the fix.Fixed by commit 78e2f3d66d (Exec: tighten jq safe-bin env checks).
OpenClaw thanks @nicky-cc of Tencent zhuque Lab https://github.com/Tencent/AI-Infra-Guard for reporting.
{
"nvd_published_at": null,
"github_reviewed_at": "2026-03-31T23:56:13Z",
"cwe_ids": [
"CWE-200"
],
"severity": "HIGH",
"github_reviewed": true
}