Loading vulnerability…
CVE-2026-67216 is a denial-of-service vulnerability in cJSON through version 1.7.19 caused by inefficient algorithmic complexity in the cJSON_Compare() function. During object equality checks, the function recursively traverses each shared subtree twice, once in each direction, and does so without a recursion depth guard. This causes the comparison cost to grow exponentially with nesting depth. As a result, even a small but deeply nested JSON document can trigger extremely long processing times when compared for equality against a structurally equal reference object. Applications that pass attacker-influenced JSON into cJSON_Compare() are exposed to CPU exhaustion and resulting availability loss.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific cJSON vulnerability included in AISLE's public registry growth summary.
An inefficient algorithmic complexity denial-of-service vulnerability in cJSON's cJSON_Compare() function that causes exponential CPU consumption on deeply nested, structurally equal JSON input.
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.