CVE-2026-32316: jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.79% (FIRST EPSS); higher than 56.5% of all records.
- 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: azl3 jq 1.7.1-4 on Azure Linux 3.0 1.7.1-5; cbl2 jq 1.6-5 on CBL Mariner 2.0 1.6-6; cbl2 jq 1.6-5 on CBL-Mariner 2.0 1.6-6.
Low priority for now. Upgrade to azl3 jq 1.7.1-4 on Azure Linux 3.0 1.7.1-5; cbl2 jq 1.6-5 on CBL Mariner 2.0 1.6-6; cbl2 jq 1.6-5 on CBL-Mariner 2.0 1.6-6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 13, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.7% · 56th percentile
- CWE
- CWE-122
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jqlang | jq | cpe:2.3:a:jqlang:jq |
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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.22 | jq | before 1.8.2-r0 | 1.8.2-r0 |
| Debian:12 | jq | before 1.6-2.1+deb12u3 | 1.6-2.1+deb12u3 |
| Debian:13 | jq | before 1.7.1-6+deb13u3 | 1.7.1-6+deb13u3 |
| Debian:14 | jq | before 1.8.1-5 | 1.8.1-5 |
| openSUSE:Leap 16.0 | jq | before 1.7.1-160000.3.1 | 1.7.1-160000.3.1 |
| openSUSE:Tumbleweed | jq | before 1.8.1-3.1 | 1.8.1-3.1 |
| Red Hat:hummingbird:1 | jq | before 0:1.8.1-3.hum1 | 0:1.8.1-3.hum1 |
| Red Hat:hummingbird:1 | jq-devel | before 0:1.8.1-3.hum1 | 0:1.8.1-3.hum1 |
| SUSE:Linux Enterprise Micro 5.3 | jq | before 1.6-150000.3.20.1 | 1.6-150000.3.20.1 |
| SUSE:Linux Micro 6.0 | jq | before 1.6-6.1 | 1.6-6.1 |
| SUSE:Linux Micro 6.0 | jq | before 1.7.1-1.1 | 1.7.1-1.1 |
| SUSE:Linux Micro 6.1 | jq | before 1.7.1-slfo.1.1_3.1 | 1.7.1-slfo.1.1_3.1 |
| SUSE:Linux Micro 6.2 | jq | before 1.7.1-160000.3.1 | 1.7.1-160000.3.1 |
Same product
jqlang: all recordsOther 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 seed30Monitor
- CVE-2025-48060AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt)30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-49014Jun 19, 2025 · jq heap use after free vulnerability in f_strflocaltime22Monitor
- ← EarlierCVE-2025-9403Aug 24, 2025 · jqlang jq JSON jq_test.c run_jq_tests assertion7Monitor
- Later →CVE-2026-33947Apr 13, 2026 · jq: Unbounded Recursion in jv_setpath(), jv_getpath() and delpaths_sorted()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 jq 1.7.1-4 on Azure Linux 3.0 | 1.7.1-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 jq 1.6-5 on CBL Mariner 2.0 | 1.6-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 jq 1.6-5 on CBL-Mariner 2.0 | 1.6-6 · Release Notes | Microsoft (MSRC) |
| alpine:jq | 1.8.2-r0 · Alpine:v3.22 | Package registry (OSV) |
| debian:jq | 1.6-2.1+deb12u2 · Debian:12 | Package registry (OSV) |
| debian:jq | 1.6-2.1+deb12u3 · Debian:12 | Package registry (OSV) |
| opensuse:jq | 1.8.1-3.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:jq | 0:1.8.1-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:jq-devel | 0:1.8.1-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:jq | 1.7.1-160000.3.1 · SUSE:Linux Micro 6.2 | Package 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, 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
Weakness class (CWE)
CWE-122 · Heap-based Buffer OverflowCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.