AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt)
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.55% (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-4; cbl2 jq 1.6-4 on CBL Mariner 2.0 1.6-4; cbl2 jq 1.6-4 on CBL-Mariner 2.0 1.6-4.
Low priority for now. Upgrade to azl3 jq 1.7.1-4 on Azure Linux 3.0 1.7.1-4; cbl2 jq 1.6-4 on CBL Mariner 2.0 1.6-4; cbl2 jq 1.6-4 on CBL-Mariner 2.0 1.6-4 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 up to and including 1.7.1, a heap-buffer-overflow is present in function `jv_string_vfmt` in the jq_fuzz_execute harness from oss-fuzz. This crash happens on file jv.c, line 1456 `void* p = malloc(sz);`. As of time of publication, no patched versions are available.
- BDU:2025-06686
- ALSA-2025:10585
- ALSA-2025:10618
- DLA-4307-1
- openSUSE-SU-2025:15233-1
- openSUSE-SU-2026:21248-1
- RHSA-2025:10585
- RHSA-2025:10613
- RHSA-2025:10615
- RHSA-2025:10616
- RHSA-2025:10618
- RHSA-2025:10619
- RHSA-2025:10620
- RHSA-2025:10621
- RHSA-2025:10622
- RHSA-2025:12882
- RLSA-2025:10585
- RLSA-2025:10618
- RLSA-2025:12882
- SUSE-SU-2025:02915-1
- Published
- May 21, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 45th percentile
- CWE
- CWE-121
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 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
- 7.7
- 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: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
- Proof of concept exists, no weaponized module
- 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.7.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
- <= 1.7.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | jq | before 1.6-11.el8_10 | 1.6-11.el8_10 |
| AlmaLinux:8 | jq-devel | before 1.6-11.el8_10 | 1.6-11.el8_10 |
| AlmaLinux:9 | jq | before 1.6-17.el9_6.2 | 1.6-17.el9_6.2 |
| AlmaLinux:9 | jq-devel | before 1.6-17.el9_6.2 | 1.6-17.el9_6.2 |
| Alpine:v3.22 | jq | before 1.8.0-r0 | 1.8.0-r0 |
| Debian:11 | jq | before 1.6-2.1+deb11u1 | 1.6-2.1+deb11u1 |
| Debian:12 | jq | before 1.6-2.1+deb12u1 | 1.6-2.1+deb12u1 |
| Debian:13 | jq | before 1.7.1-6+deb13u1 | 1.7.1-6+deb13u1 |
| Debian:14 | jq | before 1.8.0-1 | 1.8.0-1 |
| openSUSE:Leap 15.6 | jq | before 1.6-150000.3.9.1 | 1.6-150000.3.9.1 |
| 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-1.1 | 1.8.1-1.1 |
| Red Hat:enterprise_linux:10.0 | jq | before 0:1.7.1-8.el10_0.1 | 0:1.7.1-8.el10_0.1 |
| Red Hat:enterprise_linux:10.0 | jq-debuginfo | before 0:1.7.1-8.el10_0.1 | 0:1.7.1-8.el10_0.1 |
| Red Hat:enterprise_linux:10.0 | jq-debugsource | before 0:1.7.1-8.el10_0.1 | 0:1.7.1-8.el10_0.1 |
| Red Hat:enterprise_linux:10.0 | jq-devel | before 0:1.7.1-8.el10_0.1 | 0:1.7.1-8.el10_0.1 |
| Red Hat:enterprise_linux:8::appstream | jq | before 0:1.6-11.el8_10 | 0:1.6-11.el8_10 |
| Red Hat:enterprise_linux:8::appstream | jq-debuginfo | before 0:1.6-11.el8_10 | 0:1.6-11.el8_10 |
| Red Hat:enterprise_linux:8::appstream | jq-debugsource | before 0:1.6-11.el8_10 | 0:1.6-11.el8_10 |
| Red Hat:enterprise_linux:8::crb | jq-devel | before 0:1.6-11.el8_10 | 0:1.6-11.el8_10 |
| Red Hat:enterprise_linux:9::baseos | jq | before 0:1.6-17.el9_6.2 | 0:1.6-17.el9_6.2 |
| Red Hat:enterprise_linux:9::baseos | jq-debuginfo | before 0:1.6-17.el9_6.2 | 0:1.6-17.el9_6.2 |
| Red Hat:enterprise_linux:9::baseos | jq-debugsource | before 0:1.6-17.el9_6.2 | 0:1.6-17.el9_6.2 |
| Red Hat:enterprise_linux:9::crb | jq-devel | before 0:1.6-17.el9_6.2 | 0:1.6-17.el9_6.2 |
+29
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-2026-32316jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-50268Dec 13, 2023 · jq has stack-based buffer overflow in decNaNs22Monitor
- ← EarlierCVE-2024-23337May 21, 2025 · jq has signed integer overflow in jv.c:jvp_array_write26Monitor
- Later →CVE-2025-49014Jun 19, 2025 · jq heap use after free vulnerability in f_strflocaltime22Monitor
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-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 jq 1.6-4 on CBL Mariner 2.0 | 1.6-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 jq 1.6-4 on CBL-Mariner 2.0 | 1.6-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| cm2 jq 1.6-4 on CBL Mariner 2.0 | 1.6-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:jq | 1.6-17.el9_6.2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:jq-devel | 1.6-17.el9_6.2 · AlmaLinux:9 | Package registry (OSV) |
| alpine:jq | 1.8.0-r0 · Alpine:v3.22 | Package registry (OSV) |
| debian:jq | 1.6-2.1+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:jq | 1.6-150000.3.9.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:jq | 0:1.6-17.el9_6.2 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:jq-debuginfo | 0:1.6-17.el9_6.2 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:jq-debugsource | 0:1.6-17.el9_6.2 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:jq-devel | 0:1.6-17.el9_6.2 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| rocky linux:jq | 0:1.6-17.el9_6.2 · Rocky Linux:9 | Package registry (OSV) |
| suse:jq | 1.6-150000.3.9.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2025-11-16 |
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.
- Published
- First PoC+178 d
- TodayOct 25, 2026+521 d
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.
No commit or PR link among the references.
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
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-121 · Stack-based Buffer OverflowCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.