CVE-2026-34588
OpenEXR wavelet decode overflow leads to OOB reads/writes.
Is CVE-2026-34588 being exploited?
Not confirmed. CVE-2026-34588 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-34588?
CVE-2026-34588 is rated High with a CVSS score of 8.6. 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-34588?
Yes. A fix has been recorded for CVE-2026-34588. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-34588 affect?
CVE-2026-34588 affects OpenEXR libOpenEXR 3.1.0–3.2.6, 3.3.0–3.3.8, 3.4.0–3.4.8. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-34588?
Upgrade to 3.2.7/3.3.9/3.4.9 or newer.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Memory corruption via crafted EXR file during in-place wavelet decode; may crash or execute code.
Patch when possible
- affected>= 3.1.0 and <= 3.1.13
- affected>= 3.2.0 and < 3.2.7
- affected>= 3.3.0 and < 3.3.9
- affected>= 3.4.0 and < 3.4.9
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.