Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-33947: jq: Unbounded Recursion in jv_setpath(), jv_getpath() and delpaths_sorted()

Noroxi assessment

Priority: Monitor (action score 22/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.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. 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. In versions 1.8.1 and below, functions jv_setpath(), jv_getpath(), and delpaths_sorted() in jq's src/jv_aux.c use unbounded recursion whose depth is controlled by the length of a caller-supplied path array, with no depth limit enforced. An attacker can supply a JSON document containing a flat array of ~65,000 integers (~200 KB) that, when used as a path argument by a trusted jq filter, exhausts the C call stack and crashes the process with a segmentation fault (SIGSEGV). This bypass works because the existing MAX_PARSING_DEPTH (10,000) limit only protects the JSON parser, not runtime path operations where arrays can be programmatically constructed to arbitrary lengths. The impact is denial of service (unrecoverable crash) affecting any application or service that processes untrusted JSON input through jq's setpath, getpath, or delpaths builtins. This issue has been addressed in commit fb59f1491058d58bdc3e8dd28f1773d1ac690a1f.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 13, 2026
Updated
Oct 26, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · GitHub_M
6.2
0.7 point gap

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.

Follow CVE-2026-33947

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for jqlang records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

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

    • < fb59f1491058d58bdc3e8dd28f1773d1ac690a1faffected

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+deb13u21.7.1-6+deb13u2
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
Red Hat:hummingbird:1jq-develbefore 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.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

Same product

jqlang: all records

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-2026-32316jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-49014Jun 19, 2025 · jq heap use after free vulnerability in f_strflocaltime
    22Monitor
  • ← EarlierCVE-2025-9403Aug 24, 2025 · jqlang jq JSON jq_test.c run_jq_tests assertion
    7Monitor
  • Later →CVE-2026-39956Apr 13, 2026 · jq: Missing runtime type checks for _strindices lead to crash and limited memory disclosure
    24Monitor

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
azl3 jq 1.7.1-4 on Azure Linux 3.01.7.1-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 jq 1.6-5 on CBL Mariner 2.01.6-6 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 jq 1.6-5 on CBL-Mariner 2.01.6-6 · Release NotesMicrosoft (MSRC)
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)
red hat:jq-devel0: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.

Credits

All researchers

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.

  • CVE-2026-4777073 days apartjq: stack overflow in deep structural equality
    27Monitor
  • CVE-2026-4389628 days apartjq: Stack Overflow in Recursive Object Merge
    22Monitor
  • CVE-2026-4061228 days apartjq: Stack overflow via unbounded recursion in jv_contains
    21Monitor
  • CVE-2026-4477728 days apartjq: stack overflow in module loading on mutual `include`
    21Monitor

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

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • 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
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-674 · Uncontrolled Recursion

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/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

Show all references (1 more)

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

All records