CVE Tools
Track your stack

CVE-2025-48060

AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt)

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

CVSS 3.17.5HighEPSS percentile47th0.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
Public exploit: 1 sourceFixVendor fixNo build named by the sources
Check it yourself

OpenVAS · 26 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.127949

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.7.1Upgrade to: after 1.7.1Stated by: NVD
  • ООО «РусБИТех-Астра» Astra Linux Special EditionAffected: 1.7Upgrade to: not statedStated by: BDU
  • Stephen Dolan jqAffected: до 1.7.1 включительноUpgrade to: not statedStated by: BDU
  • ООО «НЦПР» МСВСфераAffected: 9.5Upgrade to: not statedStated by: BDU
  • АО «НППКТ» ОСОН ОСнова ОnyxAffected: до 3.1Upgrade 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

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.

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.

EPSS47th
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.6% chance of exploitation activity in the next 30 days, which ranks it in the 47th percentile of scored CVEs.

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

Lifecycle

The patch came 123 days before any public exploit.

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

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • 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 HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

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

Sources

References in the record

And 5 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.