CVE-2026-39979: jq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39979?
CVE-2026-39979 has a medium severity rating due to its potential to cause out-of-bounds reads.
How do I fix CVE-2026-39979?
To fix CVE-2026-39979, update jq to a version newer than 2f09060afab23fe9390cce7cb860b10416e1bf5f.
What software is affected by CVE-2026-39979?
CVE-2026-39979 affects versions of jq prior to 2f09060afab23fe9390cce7cb860b10416e1bf5f.
What is the nature of the vulnerability in CVE-2026-39979?
CVE-2026-39979 involves an out-of-bounds read in the jv_parse_sized() function when handling non-NUL-terminated buffers.
Is there a known exploit for CVE-2026-39979?
As of now, there are no publicly disclosed exploits specifically targeting CVE-2026-39979.