CVE-2026-40164 is a denial-of-service vulnerability in jq caused by use of MurmurHash3 with a fixed, publicly known seed for JSON object hash-table operations. An attacker can construct JSON object keys that collide in the same hash bucket. Processing such an object degrades hash-table lookups from expected O(1) behavior to O(n), causing jq expressions operating on the object to exhibit O(n²) behavior and consume excessive CPU. A relatively small crafted JSON object, approximately 100 KB, can trigger the condition.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A jq denial-of-service vulnerability caused by crafted JSON objects that trigger hash collisions.
A denial-of-service vulnerability in jq caused by crafted JSON objects that trigger hash collisions.
A jq denial-of-service vulnerability caused by crafted JSON objects that trigger hash collisions.
A denial-of-service vulnerability in jq caused by crafted JSON objects that trigger hash collisions.
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.