Skip to content
Noroxi
CVE-2026-32316· NVD / CVE Program· CNA GitHub_M

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Apr 13, 2026
Updated
Jun 17, 2026
EPSS
0.5% · 39th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
8.2
0.7 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
jqlangjq

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • jqlang jqup to 1.8.1 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • jqlang jq

    • < e47e56d226519635768e6aab2f38f0ab037c09e5affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.22jqbefore 1.8.2-r01.8.2-r0
Debian:12jqbefore 1.6-2.1+deb12u21.6-2.1+deb12u2
Debian:13jqbefore 1.7.1-6+deb13u31.7.1-6+deb13u3
Debian:14jqbefore 1.8.1-51.8.1-5
openSUSE:Leap 16.0jqbefore 1.7.1-160000.3.11.7.1-160000.3.1
openSUSE:Tumbleweedjqbefore 1.8.1-3.11.8.1-3.1
Red Hat:hummingbird:1jqbefore 0:1.8.1-3.hum10:1.8.1-3.hum1
SUSE:Linux Enterprise Micro 5.3jqbefore 1.6-150000.3.20.11.6-150000.3.20.1
SUSE:Linux Micro 6.0jqbefore 1.7.1-1.11.7.1-1.1
SUSE:Linux Micro 6.0jqbefore 1.6-6.11.6-6.1
SUSE:Linux Micro 6.1jqbefore 1.7.1-slfo.1.1_3.11.7.1-slfo.1.1_3.1
SUSE:Linux Micro 6.2jqbefore 1.7.1-160000.3.11.7.1-160000.3.1

Other highest-scoring records for the same primary product.

  • CVE-2024-53427decNumberCopy in decNumber.c in jq through 1.7.1 does not properly consider that NaN is interpreted as numeric, which has a resultant stack-
    32Monitor
  • CVE-2026-40164jq: Algorithmic complexity DoS via hardcoded MurmurHash3 seed
    30Monitor
  • CVE-2025-48060AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt)
    30Monitor
  • CVE-2023-49355decToString in decNumber/decNumber.c in jq 88f01a7 has a one-byte out-of-bounds write via the " []-1.2e-1111111111" input.
    30Monitor
  • CVE-2026-49839jq --rawfile invalid-state reuse after String too long causes heap-buffer-overflow
    28Monitor
  • CVE-2026-54679jq: potential integer overflow in jvp_string_append
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:jq1.8.2-r0 · Alpine:v3.22Package registry (OSV)
debian:jq1.6-2.1+deb12u2 · Debian:12Package registry (OSV)
opensuse:jq1.8.1-3.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:jq0:1.8.1-3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:jq1.7.1-160000.3.1 · SUSE:Linux Micro 6.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records