cve.bz

CVE-2026-32316 jqlang jq: Heap-based Buffer Overflow

7.5 highExploit referenceEPSS 0.8%Fix available

High (7.5) in jqlang jq. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-04-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-122 Heap-based Buffer Overflow
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-32316 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-32316?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-32316?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-32316 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-32316

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-32316](https://cve.bz/cve/badge/CVE-2026-32316.svg)](https://cve.bz/cve/CVE-2026-32316)

HTML:

<a href="https://cve.bz/cve/CVE-2026-32316"><img src="https://cve.bz/cve/badge/CVE-2026-32316.svg" alt="CVE-2026-32316"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
jqlang:jqthrough 1.8.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12jq1.6-2.1+deb12u3DEBIAN-CVE-2026-32316
Debian13jq1.7.1-6+deb13u3DEBIAN-CVE-2026-32316
Debian14jq1.8.1-5DEBIAN-CVE-2026-32316
Ubuntu22.04:LTSjq1.6-2.1ubuntu3.2UBUNTU-CVE-2026-32316 USN-8202-1
Ubuntu24.04:LTSjq1.7.1-3ubuntu0.24.04.2UBUNTU-CVE-2026-32316 USN-8202-1
Ubuntu25.10jq1.8.1-3ubuntu1.1UBUNTU-CVE-2026-32316 USN-8202-1
Ubuntu26.04:LTSjq1.8.1-4ubuntu2UBUNTU-CVE-2026-32316
UbuntuPro:14.04:LTSjqno fix listedUBUNTU-CVE-2026-32316 USN-8202-1
UbuntuPro:16.04:LTSjq1.5+dfsg-1ubuntu0.1+esm4UBUNTU-CVE-2026-32316 USN-8202-1
UbuntuPro:18.04:LTSjq1.5+dfsg-2ubuntu0.1~esm2UBUNTU-CVE-2026-32316 USN-8202-1
UbuntuPro:20.04:LTSjq1.6-1ubuntu0.20.04.1+esm2UBUNTU-CVE-2026-32316 USN-8202-1
Red Hathummingbird:1jq, jq-devel0:1.8.1-3.hum1RHSA-2026:8579
SUSELinux Enterprise Micro 5.3, Linux Enterprise Micro 5.4, Linux Enterprise Micro 5.5 and 1 morejq1.6-150000.3.20.1SUSE-SU-2026:2983-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0jq1.7.1-160000.3.1SUSE-SU-2026:22566-1
SUSELinux Micro 6.0jq1.6-6.1SUSE-SU-2026:22705-1
SUSELinux Micro 6.0jq1.7.1-1.1SUSE-SU-2026:23873-1
SUSELinux Micro 6.1jq1.7.1-slfo.1.1_3.1SUSE-SU-2026:22664-1
SUSELinux Micro 6.2jq1.7.1-160000.3.1SUSE-SU-2026:22545-1
openSUSELeap 16.0jq1.7.1-160000.3.1openSUSE-SU-2026:21248-1
openSUSETumbleweedjq1.8.1-3.1openSUSE-SU-2026:10850-1
Alpinev3.21, v3.22, v3.23 and 1 morejq1.8.2-r0ALPINE-CVE-2026-32316
Azure Linux3jq1.7.1-5AZL-82922
Alpaquita23, streamjq1.8.1-r1BELL-CVE-2026-32316
Alpaquita25jq1.8.1-r2BELL-CVE-2026-32316

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This Moderate impact vulnerability in `jq`, a command-line JSON processor, allows for a Denial of Service or potential arbitrary code execution. The flaw occurs when `jq` processes untrusted queries that generate excessively large strings, leading to an integer overflow and heap-based buffer overflow. Red Hat products that utilize `jq` for processing JSON data are affected if they handle untrusted `jq` queries.

Red Hat's mitigation

To mitigate this issue, avoid processing untrusted or unvalidated JSON input with the `jq` utility. Ensure that any scripts or automated processes utilizing `jq` only operate on trusted data sources. Restricting the execution of `jq` to trusted users and environments can also reduce exposure.

ProductPackageStateAdvisory
Red Hat Hardened Imagesjq-main-1.8.1-3.hum1Fixed 2026-04-16RHSA-2026:8579
Red Hat Ansible Automation Platform 2automation-controllerFix deferred
Red Hat Ansible Automation Platform 2redhat-user-workloads/controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2redhat-user-workloads/hub-rhel9Fix deferred
Red Hat Ceph Storage 4jqFix deferred
Red Hat Enterprise Linux 10jqFix deferred
Red Hat Enterprise Linux 8jqFix deferred
Red Hat Enterprise Linux 9jqFix deferred
Red Hat OpenShift Container Platform 4rhcosFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-32316.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON