CVE-2026-34545 is a heap-based buffer overflow in OpenEXR versions 3.4.0 through versions before 3.4.7. Decoding a crafted EXR image using HTJ2K compression and a channel width of 32768 allows attacker-controlled data to be written beyond the output heap buffer. The write primitive is 2 bytes per overflow iteration on one decoding path or 4 bytes on another, repeating for each additional pixel past the overflow point. Exploitation can potentially lead to remote code execution in applications using the affected decoder.
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.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A locally exploitable vulnerability with high confidentiality, integrity, and availability impacts. The CVSS v3 and v4 vectors indicate that user interaction is required. Exploits and a patch are available, but the content does not identify the affected product or underlying flaw.
A heap-based buffer overflow in OpenEXR image decoding that can be triggered by a crafted .exr file using HTJ2K compression, potentially leading to remote code execution.
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.