jq is a command-line JSON processor. In 1.8.1 and earlier, jq accepts embedded NUL bytes in import paths at the jq-language level, but later resolves those paths through C string operations during module and data-file lookup. This creates a mismatch between the logical import string that policy or audit code may validate and the on-disk path that jq actually opens.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/jqlang/jq/security/advisories/GHSA-7q7g-mrq3-phxr Exploit, Mitigation, Vendor Advisory
- https://github.com/jqlang/jq/security/advisories/GHSA-7q7g-mrq3-phxr Exploit, Mitigation, 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 4.4 · 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-7q7g-mrq3-phxr Exploit, Mitigation, Vendor Advisory
- https://github.com/jqlang/jq/security/advisories/GHSA-7q7g-mrq3-phxr Exploit, Mitigation, Vendor Advisory