jq is a command-line JSON processor. Prior to 1.8.2,` jq --rawfile` can turn a handled oversized-string error into invalid-state reuse and a real heap out-of-bounds write in assertion-disabled builds. When jv_load_file(raw=1) reads an attacker-controlled file, it repeatedly appends file chunks to the same jv string accumulator. Once jv_string_append_buf() returns jv_invalid_with_msg("String too long"), the raw-file loop does not stop. If the file contains at least one more byte, the next loop iteration appends a new chunk to an object that is already invalid. With assertions enabled this aborts in jvp_string_ptr(). With assertions disabled, the invalid object is interpreted as a string object and ASan reports heap-buffer-overflow. This vulnerability is fixed in 1.8.2.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/jqlang/jq/security/advisories/GHSA-cfh2-vwfq-qfmm Exploit, Vendor Advisory
- https://github.com/jqlang/jq/security/advisories/GHSA-cfh2-vwfq-qfmm 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 7.1 · jqlangNVD modified 2026-10-25 22:10
Affected (CPE criteria) 1
cpe:2.3:a:jqlang:jq:*:*:*:*:*:*:*:*
References 2
- https://github.com/jqlang/jq/security/advisories/GHSA-cfh2-vwfq-qfmm Exploit, Vendor Advisory
- https://github.com/jqlang/jq/security/advisories/GHSA-cfh2-vwfq-qfmm Exploit, Vendor Advisory