jq is a command-line JSON processor. In 1.8.1 and earlier, Top-level jq programs loaded from a file with -f are truncated at the first embedded NUL byte on current upstream HEAD. A crafted filter file such as . followed by \x00 and arbitrary suffix compiles and executes as only the prefix before the NUL. This leaves jq with a post-CVE-2026-33948 prefix/full-buffer mismatch on the compilation path even though the JSON parser path has already been fixed.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/jqlang/jq/security/advisories/GHSA-vf2h-chrj-q3fg Exploit, Vendor Advisory
- https://github.com/jqlang/jq/security/advisories/GHSA-vf2h-chrj-q3fg Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.5 · jqlangNVD modified 2026-10-26 18:10
Affected (CPE criteria) 1
cpe:2.3:a:jqlang:jq:*:*:*:*:*:*:*:*
References 2
- https://github.com/jqlang/jq/security/advisories/GHSA-vf2h-chrj-q3fg Exploit, Vendor Advisory
- https://github.com/jqlang/jq/security/advisories/GHSA-vf2h-chrj-q3fg Exploit, Vendor Advisory