CVE-2026-44777: jq: stack overflow in module loading on mutual `include`
Noroxi assessment
Priority: Monitor (action score 21/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.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 jq 1.7.1-5 on Azure Linux 3.0 1.7.1-6; azl3 jq 1.7.1-6 on Azure Linux 3.0 1.7.1-6.
Low priority for now. Upgrade to azl3 jq 1.7.1-5 on Azure Linux 3.0 1.7.1-6; azl3 jq 1.7.1-6 on Azure Linux 3.0 1.7.1-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 1.8.2rc1 and earlier, the ordinary module loader recurses without cycle detection when two otherwise valid modules include each other.
- Published
- May 11, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-674
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 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
- 5.4
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
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.2rc1affected
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.2 inclusive
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 | 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+deb13u3 | 1.7.1-6+deb13u3 |
| Debian:14 | jq | before 1.8.1-6 | 1.8.1-6 |
| openSUSE:Leap 16.0 | jq | before 1.7.1-160000.4.1 | 1.7.1-160000.4.1 |
| openSUSE:Tumbleweed | jq | before 1.8.1-3.1 | 1.8.1-3.1 |
| Red Hat:hummingbird:1 | jq | before 0:1.8.2-0.1.hum1 | 0:1.8.2-0.1.hum1 |
| Red Hat:hummingbird:1 | jq-devel | before 0:1.8.2-0.1.hum1 | 0:1.8.2-0.1.hum1 |
| SUSE:Linux Enterprise Micro 5.3 | jq | before 1.7.1-150000.3.25.1 | 1.7.1-150000.3.25.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_4.1 | 1.7.1-slfo.1.1_4.1 |
| SUSE:Linux Micro 6.2 | jq | before 1.7.1-160000.4.1 | 1.7.1-160000.4.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-2026-43895May 11, 2026 · jq: Embedded NUL in jq import paths causes local redaction-policy bypass and preserves sensitive fields in published artifacts17Monitor
- ← EarlierCVE-2026-43896May 11, 2026 · jq: Stack Overflow in Recursive Object Merge22Monitor
- Later →CVE-2026-47770Jun 25, 2026 · jq: stack overflow in deep structural equality27Monitor
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-5 on Azure Linux 3.0 | 1.7.1-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 jq 1.7.1-6 on Azure Linux 3.0 | 1.7.1-6 · CBL-Mariner Releases | 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.2-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:jq-devel | 0:1.8.2-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:jq | 1.7.1-160000.4.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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-4777045 days apartjq: stack overflow in deep structural equality27Monitor
- CVE-2026-438960 days apartjq: Stack Overflow in Recursive Object Merge22Monitor
- CVE-2026-3394728 days apartjq: Unbounded Recursion in jv_setpath(), jv_getpath() and delpaths_sorted()22Monitor
- CVE-2026-406120 days apartjq: Stack overflow via unbounded recursion in jv_contains21Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · 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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-674 · Uncontrolled RecursionCVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P/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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →