CVE-2026-34543
Info disclosure in OpenEXR decoding via crafted EXR files (heap leak).
Is CVE-2026-34543 being exploited?
Not confirmed. CVE-2026-34543 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-34543?
CVE-2026-34543 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-34543?
Yes. A fix has been recorded for CVE-2026-34543. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-34543 affect?
CVE-2026-34543 affects OpenEXR 3.4.0-3.4.7. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-34543?
Upgrade to OpenEXR 3.4.8+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Heap memory leak via EXR pixel decoding; reading a crafted file leaks sensitive heap data; no user interaction.
Patch when possible
- affected>= 3.4.0 and < 3.4.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.