CVE Tools
Track your stack

CVE-2025-9403

jqlang jq JSON jq_test.c run_jq_tests assertion

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

CVSS 3.13.3LowEPSS percentile13th0.2% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
Public exploit: 1 sourceFixVendor fixNo build named by the sources
Check it yourself

OpenVAS · 7 checks

e.g. OID 1.3.6.1.4.1.25623.1.1.16.2026.2780

Run the check

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Jqlang JqAffected: 1.0Upgrade to: not statedAffected: 1.1Upgrade to: not statedAffected: 1.2Upgrade to: not statedAffected: 1.3Upgrade to: not stated + 3 more branchesStated by: CVE record
  • ООО «Ред Софт» РЕД ОСAffected: 7.3Upgrade to: not statedStated by: BDU
  • Stephen Dolan jqAffected: до 1.6Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS13th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 13th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

A public exploit existed 53 days before the patch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Public exploit / PoCsource: other
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Scored 3.3 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 4 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Jq, not every advisory. This one: public exploit.