Skip to content
Fencer Intel
low 3.3

CVE-2025-9403 json

jqlang jq JSON jq_test.c run_jq_tests assertion

published last yr. modified 4mo ago also EUVD-2025-25716

cvss
3.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

A vulnerability was determined in jqlang jq up to 1.6. Impacted is the function run_jq_tests of the file jq_test.c of the component JSON Parser. Executing manipulation can lead to reachable assertion. The attack requires local access. The exploit has been publicly disclosed and may be utilized. Other versions might be affected as well.

Patch / fix

  • jq SLES for SAP 15 SP6, SLES for SAP 15 SP5, SLES for SAP 15 SP4 +11 more 1.7.1-150000.3.25.1
  • jq Linux Micro 6.0 1.7.1-1.1
  • jq Linux Micro 6.0 1.6-6.1
  • jq SLE Module for Basesystem 15 SP7, SLE Micro 5.5, SLE Micro 5.4 +3 more 1.6-150000.3.12.1

suse advisories SUSE-SU-2026:4275-1SUSE-SU-2026:23873-1SUSE-SU-2026:22705-1SUSE-SU-2026:0931-1

  • jq openSUSE Tumbleweed 1.8.2-2.1

opensuse advisories openSUSE-SU-2026:11789-1

  • jq CBL-Mariner 2.0 1.6-5
  • jq Azure Linux 3.0 1.7.1-8

azure linux advisories AZL-66678AZL-85554

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2025-9403 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-9403 updated cvss 3.3

jq: assertion failure in run_jq_tests() of the file jq_test.c

  • Red Hat Ansible Automation Platform 2 automation-controller Red Hat Ceph Storage 4 jq
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Enterprise Linux 8 jq
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 9 jq Red Hat Enterprise Linux 10 jq Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat Trusted Application Pipeline rhtap-cli/rhtap-cli-rhel9
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • vuldb.com https://vuldb.com/?submit.633170 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/jqlang/jq/issues/3393 referenced PoC, tagged "exploit" by a source, unverified
  • drive.google.com https://drive.google.com/file/d/1r8m9PhU_rk-QPj6OMcs415FcvWPD-zJY/view?usp=sharing referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 4.8 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
CNA 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:X/RC:R
CNA 3.0 3.3 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:X/RC:R
CNA 2.0 1.7 AV:L/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:ND/RC:UR
CNA 4.0 1.9 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/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
CNA 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA 2.0 1.7 AV:L/AC:L/Au:S/C:N/I:N/A:P

Affected products

  • jqlang jq

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.