Summary
OpenEXR: Heap information disclosure in PXR24 decompression via unchecked decompressed size (undopxr24impl)
Impact
- Sensitive information from heap memory may be leaked through the decoded pixel data (information disclosure).
Trigger Condition: Occurs under default settings; simply reading a malicious EXR file is sufficient to trigger the issue, without any user interaction.
Affected versions
openexr (>= 3.4.0, <= 3.4.7)
openexr (>= 3.3.0, <= 3.3.8)
openexr (>= 3.2.0, <= 3.2.6)
Security releases
openexr → 3.4.8 (pip)
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Upgrade openexr to 3.4.8 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-34543? CVE-2026-34543 is a high-severity security vulnerability in openexr (pip), affecting versions >= 3.4.0, <= 3.4.7. It is fixed in 3.4.8.
- Which versions of openexr are affected by CVE-2026-34543? openexr (pip) versions >= 3.4.0, <= 3.4.7 is affected.
- Is there a fix for CVE-2026-34543? Yes. CVE-2026-34543 is fixed in 3.4.8. Upgrade to this version or later.
- Is CVE-2026-34543 exploitable, and should I be worried? Whether CVE-2026-34543 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-34543 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-34543? Upgrade
openexrto 3.4.8 or later.