CVE-2026-39979: jq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers
Noroxi assessment
Priority: Monitor (action score 27/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.58% (FIRST EPSS).
- 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. 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.
- BDU:2026-05572
- ALSA-2026:16252
- ALSA-2026:16692
- ALSA-2026:16693
- ALSA-2026:19151
- ALSA-2026:19365
- openSUSE-SU-2026:10850-1
- openSUSE-SU-2026:21248-1
- RHSA-2026:16252
- RHSA-2026:16692
- RHSA-2026:16693
- RHSA-2026:18040
- RHSA-2026:18042
- RHSA-2026:18043
- RHSA-2026:18044
- RHSA-2026:18045
- RHSA-2026:18046
- RHSA-2026:18047
- RHSA-2026:18048
- RHSA-2026:19151
- Published
- Apr 13, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.5% · 48th percentile
- CWE
- CWE-125
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 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
- —
- CNA · GitHub_M
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N
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.
Is your version affected? Check itNoroxi 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 |
| redhat | ai inference server | cpe:2.3:a:redhat:ai_inference_server |
| redhat | ansible automation platform | cpe:2.3:a:redhat:ansible_automation_platform |
| redhat | ceph storage | cpe:2.3:a:redhat:ceph_storage |
| redhat | codeready linux builder | cpe:2.3:a:redhat:codeready_linux_builder |
| redhat | codeready linux builder eus | cpe:2.3:a:redhat:codeready_linux_builder_eus |
| redhat | hardened images | cpe:2.3:a:redhat:hardened_images |
| redhat | openshift ai | cpe:2.3:a:redhat:openshift_ai |
| redhat | openshift container platform | cpe:2.3:a:redhat:openshift_container_platform |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| redhat | enterprise linux aus | cpe:2.3:o:redhat:enterprise_linux_aus |
| redhat | enterprise linux eus | cpe:2.3:o:redhat:enterprise_linux_eus |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jqlang jqbefore 1.8.2
- redhat ai inference server3.2.0 and later · before 3.2.2
- redhat ai inference server3.3.0 and later · before 3.3.5
- redhat ansible automation platform2.0
- redhat ceph storage4.0
- redhat codeready linux builder10.0
- redhat codeready linux builder8.0
- redhat codeready linux builder9.0
- redhat codeready linux builder eus10.0
- redhat codeready linux builder eus9.4
- redhat codeready linux builder eus9.6
- redhat enterprise linux10.0
- redhat enterprise linux8.0
- redhat enterprise linux9.0
- redhat enterprise linux aus8.4
- redhat enterprise linux aus8.6
- redhat enterprise linux eus10.0
- redhat enterprise linux eus8.4
- redhat enterprise linux eus9.4
- redhat enterprise linux eus9.6
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
- < 2f09060afab23fe9390cce7cb860b10416e1bf5faffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | jq | before 1.7.1-11.el10_2.2 | 1.7.1-11.el10_2.2 |
| AlmaLinux:10 | jq | before 1.7.1-11.el10_1.0.2 | 1.7.1-11.el10_1.0.2 |
| AlmaLinux:10 | jq-devel | before 1.7.1-11.el10_2.2 | 1.7.1-11.el10_2.2 |
| AlmaLinux:10 | jq-devel | before 1.7.1-11.el10_1.0.2 | 1.7.1-11.el10_1.0.2 |
| AlmaLinux:8 | jq | before 1.6-12.el8_10 | 1.6-12.el8_10 |
| AlmaLinux:8 | jq-devel | before 1.6-12.el8_10 | 1.6-12.el8_10 |
| AlmaLinux:9 | jq | before 1.6-19.el9_7.0.2 | 1.6-19.el9_7.0.2 |
| AlmaLinux:9 | jq | before 1.6-19.el9_8.2 | 1.6-19.el9_8.2 |
| AlmaLinux:9 | jq-devel | before 1.6-19.el9_8.2 | 1.6-19.el9_8.2 |
| AlmaLinux:9 | jq-devel | before 1.6-19.el9_7.0.2 | 1.6-19.el9_7.0.2 |
| Alpine:v3.22 | jq | before 1.8.2-r0 | 1.8.2-r0 |
| Debian:12 | jq | before 1.6-2.1+deb12u2 | 1.6-2.1+deb12u2 |
| Debian:13 | jq | before 1.7.1-6+deb13u2 | 1.7.1-6+deb13u2 |
| 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:enterprise_linux_eus:10.0 | jq | before 0:1.7.1-8.el10_0.3 | 0:1.7.1-8.el10_0.3 |
| Red Hat:enterprise_linux_eus:10.0 | jq-debuginfo | before 0:1.7.1-8.el10_0.3 | 0:1.7.1-8.el10_0.3 |
| Red Hat:enterprise_linux_eus:10.0 | jq-debugsource | before 0:1.7.1-8.el10_0.3 | 0:1.7.1-8.el10_0.3 |
| Red Hat:enterprise_linux_eus:10.0 | jq-devel | before 0:1.7.1-8.el10_0.3 | 0:1.7.1-8.el10_0.3 |
| Red Hat:enterprise_linux:10.1 | jq | before 0:1.7.1-11.el10_1.0.2 | 0:1.7.1-11.el10_1.0.2 |
| Red Hat:enterprise_linux:10.1 | jq-debuginfo | before 0:1.7.1-11.el10_1.0.2 | 0:1.7.1-11.el10_1.0.2 |
| Red Hat:enterprise_linux:10.1 | jq-debugsource | before 0:1.7.1-11.el10_1.0.2 | 0:1.7.1-11.el10_1.0.2 |
| Red Hat:enterprise_linux:10.1 | jq-devel | before 0:1.7.1-11.el10_1.0.2 | 0:1.7.1-11.el10_1.0.2 |
+50
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…32Monitor
- CVE-2026-40164jq: Algorithmic complexity DoS via hardcoded MurmurHash3 seed30Monitor
- CVE-2026-32316jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-33947Apr 13, 2026 · jq: Unbounded Recursion in jv_setpath(), jv_getpath() and delpaths_sorted()22Monitor
- ← EarlierCVE-2026-39956Apr 13, 2026 · jq: Missing runtime type checks for _strindices lead to crash and limited memory disclosure24Monitor
- Later →CVE-2026-33948Apr 14, 2026 · jq: Embedded-NUL Truncation in CLI JSON Input Path Causes Prefix-Only Validation of Malformed Input11Monitor
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) |
| almalinux:jq | 1.6-12.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:jq-devel | 1.6-12.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| alpine:jq | 1.8.2-r0 · Alpine:v3.22 | Package registry (OSV) |
| debian:jq | 1.6-2.1+deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:jq | 1.8.1-3.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:jq | 0:1.6-12.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jq-debuginfo | 0:1.6-12.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jq-debugsource | 0:1.6-12.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jq-devel | 0:1.6-12.el8_10 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| rocky linux:jq | 0:1.6-12.el8_10 · Rocky Linux:8 | 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.
- CVE-2026-399560 days apartjq: Missing runtime type checks for _strindices lead to crash and limited memory disclosure24Monitor
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
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
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 (19 more)Show less
- access.redhat.com/errata/RHSA-2026:16252
- access.redhat.com/errata/RHSA-2026:16692
- access.redhat.com/errata/RHSA-2026:16693
- access.redhat.com/errata/RHSA-2026:18040
- access.redhat.com/errata/RHSA-2026:18042
- access.redhat.com/errata/RHSA-2026:18043
- access.redhat.com/errata/RHSA-2026:18044
- access.redhat.com/errata/RHSA-2026:18045
- access.redhat.com/errata/RHSA-2026:18046
- access.redhat.com/errata/RHSA-2026:18047
- access.redhat.com/errata/RHSA-2026:18048
- access.redhat.com/errata/RHSA-2026:19151
- access.redhat.com/errata/RHSA-2026:19365
- access.redhat.com/errata/RHSA-2026:23233
- access.redhat.com/errata/RHSA-2026:23245
- access.redhat.com/errata/RHSA-2026:25044
- access.redhat.com/errata/RHSA-2026:25096
- access.redhat.com/errata/RHSA-2026:25181
- access.redhat.com/errata/RHSA-2026:26528
Vendor advisories and official records. Exploit/PoC links are deliberately left out.