CVE-2026-34543 — openexr
Fix: AcademySoftwareFoundation/openexr@5f6d0aaCVE-2026-34543 is a CWE-908 vulnerability in openexr. A fix is available for openexr — see the affected versions and patch details below.
OpenEXR: Heap information disclosure in PXR24 decompression via unchecked decompressed size (undo_pxr24_impl)
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-34543.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
openexr🐍openexr🐍openexrReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The PXR24 decompression function undo_pxr24_impl in OpenEXR (internal_pxr24.c) ignores the actual decompressed size (outSize) returned by exr_uncompress_buffer() and instead reads from the scratch buffer based solely on the expected size (uncompressed_size) derived from the header metadata.
Additionally, exr_uncompress_buffer() (compression.c:202) treats LIBDEFLATE_SHORT_OUTPUT (where the compressed stream decompresses to fewer bytes than expected) as a successful result rather than an error.
When these two issues are combined, an attacker can craft a PXR24 EXR file containing a valid but truncated zlib stream. As a result, the decoder reads uninitialized heap memory and incorporates it into the output pixel data.
Details
This issue occurs due to the combination of two flaws.
- compression.c:202–205 — LIBDEFLATE_SHORT_OUTPUT treated as success
else if (res == LIBDEFLATE_SHORT_OUTPUT)
{
/* TODO: is this an error? */
return EXR_ERR_SUCCESS;
}
libdeflate_zlib_decompress_ex() returns LIBDEFLATE_SHORT_OUTPUT when the compressed stream is successfully decompressed but the resulting output size is smaller than the provided output buffer size. In this case, the actual number of decompressed bytes is written to actual_out. However, the function does not treat this condition as an error and instead returns success.
- internal_pxr24.c:279–287 — outSize return value ignored
rstat = exr_uncompress_buffer(
decode->context, compressed_data, comp_buf_size,
scratch_data, scratch_size, &outSize); // outSize = actual bytes written
if (rstat != EXR_ERR_SUCCESS) return rstat;
// outSize is never referenced afterwards.
// The loop below reads the entire scratch_data buffer based on
// uncompressed_size (the header-derived expected size).
for (int y = 0; y < decode->chunk.height; ++y) { ... }
After exr_uncompress_buffer() returns success, the code does not verify whether the actual decompressed size (outSize) matches the expected size (uncompressed_size). The subsequent byte-plane reconstruction loop reads from the scratch buffer up to uncompressed_size bytes. As a result, the region between outSize and uncompressed_size consists of uninitialized heap memory, which is then read by the decoder.
Affected component
- src/lib/OpenEXRCore/internal_pxr24.c — undo_pxr24_impl() (line 261–399)
- src/lib/OpenEXRCore/compression.c — exr_uncompress_buffer() (line 202–205)
PoC
Please refer to the atta poc.zip ched archive file and proceed after extracting it.
- git clone https://github.com/AcademySoftwareFoundation/openexr.git
- mv poc openexr/
- cd openexr
- docker build -f poc/Dockerfile -t pxr24-poc .
- docker run --rm pxr24-poc
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | openexr | ≥ 3.4.0&&< 3.4.8 | 3.4.8pip install --upgrade 'openexr==3.4.8' |
| 🐍PyPI | openexr | ≥ 3.3.0 | No fix |
| 🐍PyPI | openexr | ≥ 3.2.0 | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openexr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openexr to 3.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-34543 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-34543 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-34543. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-34543 in your dependencies?
O3 Security finds CVE-2026-34543 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.