CVE-2026-32316: jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow
jq is a command-line JSON processor. An integer overflow vulnerability exists through version 1.8.1 within the jvp_string_append() and jvp_string_copy_replace_bad functions, where concatenating strings with a combined length exceeding 2^31 bytes causes a 32-bit unsigned integer overflow in the buffer allocation size calculation, resulting in a drastically undersized heap buffer. Subsequent memory copy operations then write the full string data into this undersized buffer, causing a heap buffer overflow classified as CWE-190 (Integer Overflow) leading to CWE-122 (Heap-based Buffer Overflow). Any system evaluating untrusted jq queries is affected, as an attacker can crash the process or potentially achieve further exploitation through heap corruption by crafting queries that produce extremely large strings. The root cause is the absence of string size bounds checking, unlike arrays and objects which already have size limits. The issue has been addressed in commit e47e56d226519635768e6aab2f38f0ab037c09e5.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-32316?
The severity of CVE-2026-32316 is classified as high due to its potential for heap-based buffer overflow.
How do I fix CVE-2026-32316?
To fix CVE-2026-32316, update jq to version 1.8.2 or later.
Which versions of jq are affected by CVE-2026-32316?
CVE-2026-32316 affects jq versions up to and including 1.8.1.
What type of vulnerability is CVE-2026-32316?
CVE-2026-32316 is an integer overflow vulnerability that can lead to a heap-based buffer overflow.
Is CVE-2026-32316 present in Microsoft products using jq?
Yes, CVE-2026-32316 is present in certain Microsoft products that utilize affected versions of jq up to 1.8.1.