Loading vulnerability…
CVE-2026-33900 affects ImageMagick in versions prior to 7.1.2-19 and 6.9.13-44. The flaw is in the VIFF encoder code path in coders/viff.c and is caused by an implicit truncation/wraparound when a 64-bit MagickSizeType value (used for the packets count) is converted to size_t during a call to AcquireVirtualMemory on 32-bit builds. If the computed packets value exceeds the maximum 32-bit size_t value, the allocation size is truncated to a much smaller value, while subsequent write operations continue to use the original larger 64-bit packets count. This creates a heap buffer size mismatch that can result in an out-of-bounds heap write when processing crafted VIFF image data, potentially crashing the process.
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.
3 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.