CVE-2026-39956: jq: Missing runtime type checks for _strindices lead to crash and limited memory disclosure
Noroxi assessment
Priority: Monitor (action score 24/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- 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. Prior to version 1.8.2, the _strindices builtin in jq's src/builtin.c passes its arguments directly to jv_string_indexes() without verifying they are strings, and jv_string_indexes() in src/jv.c relies solely on assert() checks that are stripped in release builds compiled with -DNDEBUG. This allows an attacker to crash jq trivially with input like _strindices(0), and by crafting a numeric value whose IEEE-754 bit pattern maps to a chosen pointer, achieve a controlled pointer dereference and limited memory read/probe primitive. Any deployment that evaluates untrusted jq filters against a release build is vulnerable. This issue has been patched in commit fdf8ef0f0810e3d365cdd5160de43db46f57ed03, which is part of version 1.8.2.
- Published
- Apr 13, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-125
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.1
- NVD has not scored this yet; the score shown is the CNA’s.
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 |
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
- < 1.8.2affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jqlang jq2026-04-02 and later · before 2026-04-08
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | jq | from 2026-04-02 · 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: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.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…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-2025-9403Aug 24, 2025 · jqlang jq JSON jq_test.c run_jq_tests assertion7Monitor
- ← EarlierCVE-2026-33947Apr 13, 2026 · jq: Unbounded Recursion in jv_setpath(), jv_getpath() and delpaths_sorted()22Monitor
- Later →CVE-2026-39979Apr 13, 2026 · jq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers27Monitor
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) |
| 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-399790 days apartjq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers27Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
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 (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.