CVE-2025-48060 is a heap-buffer-overflow vulnerability in jq, a command-line JSON processor. It affects jq versions through 1.7.1 and occurs in the jv_string_vfmt function when exercised through the oss-fuzz jq_fuzz_execute harness. The reported failing allocation is in jv.c at the malloc call associated with this string-formatting path. Some downstream notices characterize the AddressSanitizer finding as a stack-buffer-overflow, but the primary vulnerability description identifies it as a heap-buffer-overflow.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A stack buffer overflow vulnerability in jq, identified in jq_fuzz_execute and jv_string_vfmt, affecting the jq package on Rocky Linux 8 systems covered by CIQ advisory crlsa-2025_10618.
An important-severity vulnerability referenced by an AlmaLinux 9.2 local security check. Its CVSS v3 vector is CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating a remotely exploitable, low-complexity, unauthenticated flaw with high availability impact and no stated confidentiality or integrity impact.
A heap buffer overflow in jq string formatting, addressed in version 1.8.0.
Unknown
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.