Loading vulnerability…
CVE-2026-64608 is a heap type confusion vulnerability in the Apache Fory C++ implementation affecting versions 0.14.0 before 1.4.0. The flaw occurs during deserialization in compatible mode, where field-skip code paths do not correctly validate declared field types against the actual serialized data. A crafted input stream with an inconsistent schema can therefore cause the deserializer to interpret data as an incompatible type, leading to out-of-bounds memory reads and writes on the heap. The issue is limited to the C++ implementation of Apache Fory; other language implementations are not affected.
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.
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.