Description
jq is a command-line JSON processor. Prior to version 1.8.2, the _strindices builtin in jq's src/builtin.c passes its arguments directly to jv_string_indexes() without verifying they are strings, and jv_string_indexes() in src/jv.c relies solely on assert() checks that are stripped in release builds compiled with -DNDEBUG. This allows an attacker to crash jq trivially with input like _strindices(0), and by crafting a numeric value whose IEEE-754 bit pattern maps to a chosen pointer, achieve a controlled pointer dereference and limited memory read/probe primitive. Any deployment that evaluates untrusted jq filters against a release build is vulnerable. This issue has been patched in commit fdf8ef0f0810e3d365cdd5160de43db46f57ed03, which is part of version 1.8.2.
Affected products
jqlang: jq
References3
- github.com/jqlang/jq/security/advisories/GHSA-6gc3-3g9p-xx28 ExploitVendor Advisory
- github.com/jqlang/jq/security/advisories/GHSA-6gc3-3g9p-xx28 ExploitVendor Advisory
- github.com/jqlang/jq/commit/fdf8ef0f0810e3d365cdd5160de43db46f5… Patch
Metrics
- CVSS 3.1
-
6.1
MEDIUM
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H - EPSS — exploit probability
- 0% percentile: 8 · as of 12 November 2026
- CWE
- CWE-125CWE-476CWE-843
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.