CVE-2026-34543: OpenEXR Heap Information Disclosure Vulnerability

HIGH
Advisory Identifier: GHSA-vc68-257w-m432
CWE-908
Published
Advisory Summary

CVE-2026-34543 is a HIGH heap information disclosure vulnerability (CWE-908: Use of Uninitialized Resource) affecting OpenEXR libraries in the PyPI ecosystem. The issue involves heap information disclosure in pxr24 decompression via unchecked decompressed size (undo_pxr24_impl). Remediation is available by upgrading affected packages to version 3.4.8.

CVE-2026-34543 at a Glance

CVE Identifier CVE-2026-34543
GHSA Identifier GHSA-vc68-257w-m432
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-908: Use of Uninitialized Resource
Affected Product OpenEXR
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix CVE-2026-34543

To remediate this vulnerability, upgrade all affected OpenEXR dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openexr fixed: 3.4.8
pip install openexr>=3.4.8
openexr fixed: Latest secure release
pip install openexr>=Latest secure release
openexr fixed: Latest secure release
pip install openexr>=Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show openexr

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-34543, inspect your installed packages using pip:

pip show openexr

Analyze the terminal output to locate any version of OpenEXR in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.4.8), your application is affected.

Note: The pip show openexr command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-908: Use of Uninitialized Resource, where the product uses or accesses a resource that has not been initialized. In OpenEXR, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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. 1. 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. 2. 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](https://github.com/user-attachments/files/26002361/poc.zip) ched archive file and proceed after extracting it. 1. git clone https://github.com/AcademySoftwareFoundation/openexr.git 2. mv poc openexr/ 3. cd openexr 4. docker build -f poc/Dockerfile -t pxr24-poc . 5. docker run --rm pxr24-poc <img width="858" height="155" alt="스크린샷 2026-03-15 오후 4 38 18" src="https://github.com/user-attachments/assets/ded9eab6-9b92-40f7-9a0d-7b00db7e6088" /> ### 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.

CVE-2026-34543 Affected OpenEXR Versions

3 component(s)
Fixed Versions:
3.4.8
Product / Package Ecosystem Affected Versions Fixed Version
openexr
PyPI
≥ 3.4.0
< 3.4.8
3.4.8
openexr
PyPI
≥ 3.3.0
≤ 3.3.8
openexr
PyPI
≥ 3.2.0
≤ 3.2.6

References

Frequently Asked Questions

What is CVE-2026-34543?
CVE-2026-34543 is a security vulnerability in OpenEXR involving Heap information disclosure in PXR24 decompression via unchecked decompressed size (undo_pxr24_impl) under CWE-908: Use of Uninitialized Resource.
Which OpenEXR versions are affected?
Affected versions include releases prior to 3.4.8 across affected packages: openexr.
What version fixes CVE-2026-34543?
Upgrading to 3.4.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openexr affected?
Yes, openexr is affected in releases prior to 3.4.8, Latest secure release. Upgrade your dependency to 3.4.8, Latest secure release or later.
What CWE is associated with CVE-2026-34543?
CVE-2026-34543 is classified under CWE-908: Use of Uninitialized Resource (The product uses or accesses a resource that has not been initialized.).
How can I check PyPI dependencies for CVE-2026-34543?
Run the dependency tree command: 'pip show openexr'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vc68-257w-m432",
  "modified" : "2026-04-03T21:50:15Z",
  "published" : "2026-04-03T21:50:14Z",
  "aliases" : [ "CVE-2026-34543" ],
  "summary" : "OpenEXR: Heap information disclosure in PXR24 decompression via unchecked decompressed size (undo_pxr24_impl)",
  "details" : "### Summary\nThe 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.\n\nAdditionally, 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.\n\nWhen 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.\n\n### Details\nThis issue occurs due to the combination of two flaws.\n\n1. compression.c:202–205 — LIBDEFLATE_SHORT_OUTPUT treated as success\n```\nelse if (res == LIBDEFLATE_SHORT_OUTPUT)\n{\n    /* TODO: is this an error? */\n    return EXR_ERR_SUCCESS;\n}\n```\nlibdeflate_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.\n\n2. internal_pxr24.c:279–287 — outSize return value ignored\n```\nrstat = exr_uncompress_buffer(\n    decode->context, compressed_data, comp_buf_size,\n    scratch_data, scratch_size, &outSize);   // outSize = actual bytes written\n\nif (rstat != EXR_ERR_SUCCESS) return rstat;\n\n// outSize is never referenced afterwards.\n// The loop below reads the entire scratch_data buffer based on\n// uncompressed_size (the header-derived expected size).\nfor (int y = 0; y < decode->chunk.height; ++y) { ... }\n```\nAfter 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.\n\n**Affected component**\n- src/lib/OpenEXRCore/internal_pxr24.c — undo_pxr24_impl() (line 261–399)\n- src/lib/OpenEXRCore/compression.c — exr_uncompress_buffer() (line 202–205)\n\n### PoC\nPlease refer to the atta\n[poc.zip](https://github.com/user-attachments/files/26002361/poc.zip)\nched archive file and proceed after extracting it.\n\n1. git clone https://github.com/AcademySoftwareFoundation/openexr.git\n2. mv poc openexr/\n3. cd openexr\n4. docker build -f poc/Dockerfile -t pxr24-poc .\n5. docker run --rm pxr24-poc\n\n<img width=\"858\" height=\"155\" alt=\"스크린샷 2026-03-15 오후 4 38 18\" src=\"https://github.com/user-attachments/assets/ded9eab6-9b92-40f7-9a0d-7b00db7e6088\" />\n\n\n### Impact\n* Sensitive information from heap memory may be leaked through the decoded pixel data (information disclosure).\nTrigger Condition: Occurs under default settings; simply reading a malicious EXR file is sufficient to trigger the issue, without any user interaction.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "openexr"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.4.0"
      }, {
        "fixed" : "3.4.8"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.4.7"
    }
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "openexr"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.3.0"
      }, {
        "last_affected" : "3.3.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "openexr"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.2.0"
      }, {
        "last_affected" : "3.2.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-vc68-257w-m432"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34543"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AcademySoftwareFoundation/openexr/commit/5f6d0aaa9e43802917af7db90f181e88e083d3b8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/AcademySoftwareFoundation/openexr"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.4.8"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-908" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-03T21:50:14Z",
    "nvd_published_at" : "2026-04-01T21:17:01Z"
  }
}