jq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.9epss 0.6%
exploitation probability
0.6%top 57% of all CVEs
observed exploitation
nono source reports it
jq is a command-line JSON processor. In commits before 2f09060afab23fe9390cce7cb860b10416e1bf5f, the jv_parse_sized() API in libjq accepts a counted buffer with an explicit length parameter, but its error-handling path formats the input buffer using %s in jv_string_fmt(), which reads until a NUL terminator is found rather than respecting the caller-supplied length. This means that when malformed JSON is passed in a non-NUL-terminated buffer, the error construction logic performs an out-of-bounds read past the end of the buffer. The vulnerability is reachable by any libjq consumer calling jv_parse_sized() with untrusted input, and depending on memory layout, can result in memory disclosure or process termination. The issue has been patched in commit 2f09060afab23fe9390cce7cb860b10416e1bf5f.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N
Affected products
jqlang · jqReferences
https://access.redhat.com/errata/RHSA-2026:16252https://access.redhat.com/errata/RHSA-2026:16692https://access.redhat.com/errata/RHSA-2026:16693https://access.redhat.com/errata/RHSA-2026:18040https://access.redhat.com/errata/RHSA-2026:18042https://access.redhat.com/errata/RHSA-2026:18043https://access.redhat.com/errata/RHSA-2026:18044https://access.redhat.com/errata/RHSA-2026:18045https://access.redhat.com/errata/RHSA-2026:18046https://access.redhat.com/errata/RHSA-2026:18047https://access.redhat.com/errata/RHSA-2026:18048https://access.redhat.com/errata/RHSA-2026:19151