# CVE-2026-27622: OpenEXR CompositeDeepScanLine integer-overflow leads to heap OOB write > An integer overflow in OpenEXR's CompositeDeepScanLine allows heap out-of-bounds writes, potentially leading to code execution or crashes when processing malicious images. - **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 3 Mar 2026 - **Updated:** 9 Sep 2026 - **Also known as:** ALSA-2026:7682, ALSA-2026:8863, ALSA-2026:8888, CLSA-2026-1773831456, CLSA-2026-1774604404, CLSA-2026-1787317469, DEBIAN-CVE-2026-27622, ECHO-d981-9908-5125, GHSA-cr4v-6jm6-4963, JLSEC-2026-141, OESA-2026-1616, OESA-2026-1617, OESA-2026-1618, OESA-2026-1619, OESA-2026-1620, OESA-2026-1685, OESA-2026-1686, OESA-2026-1687, OESA-2026-1688, OESA-2026-1689, PYSEC-2026-2846, RHSA-2026:12338, RHSA-2026:12339, RHSA-2026:12340, RHSA-2026:12341, RHSA-2026:7678, RHSA-2026:7682, RHSA-2026:8863, RHSA-2026:8869, RHSA-2026:8870, RHSA-2026:8871, RHSA-2026:8872, RHSA-2026:8888, RLSA-2026:7682, RLSA-2026:8863, RLSA-2026:8888, ROOT-OS-DEBIAN-11-CVE-2026-27622, ROOT-OS-DEBIAN-12-CVE-2026-27622, ROOT-OS-DEBIAN-13-CVE-2026-27622, SUSE-SU-2026:20936-1, UBUNTU-CVE-2026-27622, openSUSE-SU-2026:10303-1, openSUSE-SU-2026:20433-1 ## What is CVE-2026-27622? CVE-2026-27622 is a high-severity vulnerability in Openexr Openexr, published on 3 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In CompositeDeepScanLine::readPixels, per-pixel totals are accumulated in vector total_sizes for attacker-controlled large counts across many parts, total_sizes[ptr] wraps modulo 2^32. overall_sample_count is then derived from wrapped totals and used in samples[channel].resize(overall_sample_count). Decode pointer setup/consumption proceeds with true sample counts, and write operations in core unpack (generic_unpack_deep_pointers) overrun the undersized composite sample buffer. This vulnerability is fixed in v3.2.6, v3.3.8, and v3.4.6. Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2026-27622? 7 open source packages ship an affected version, including openexr and OpenEXR. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `openexr` | PyPI | From 2.3.0 | 3.2.6, 3.3.8, 3.4.6 | | `openexr` | PyPI | From 2.3.0 | 3.2.6 | | `openexr` | PyPI | From 3.3.0 | 3.3.8 | | `openexr` | PyPI | From 3.4.0 | 3.4.6 | | `OpenEXR` | PyPI | From 2.3.0 | 3.2.6 | | `OpenEXR` | PyPI | From 3.3.0 | 3.3.8 | | `OpenEXR` | PyPI | From 3.4.0 | 3.4.6 | | `openexr` | AlmaLinux:10 | All versions | 3.1.10-8.el10_1.1 | | `openexr-devel` | AlmaLinux:10 | All versions | 3.1.10-8.el10_1.1 | | `openexr-libs` | AlmaLinux:10 | All versions | 3.1.10-8.el10_1.1 | | `OpenEXR-devel` | AlmaLinux:8 | All versions | 2.2.0-12.el8_10.1 | | `OpenEXR-libs` | AlmaLinux:8 | All versions | 2.2.0-12.el8_10.1 | | `openexr` | AlmaLinux:9 | All versions | 3.1.1-3.el9_7.1 | | `openexr-devel` | AlmaLinux:9 | All versions | 3.1.1-3.el9_7.1 | | `openexr-libs` | AlmaLinux:9 | All versions | 3.1.1-3.el9_7.1 | | `openexr` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.1.10-8.el10_1.1 | | `openexr-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.1.10-8.el10_1.1 | | `openexr-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.1.10-8.el10_1.1 | | `openexr-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.1.10-8.el10_1.1 | | `openexr-libs` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.1.10-8.el10_1.1 | | `openexr-libs-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.1.10-8.el10_1.1 | | `OpenEXR` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.0-12.el8_10.1 | | `OpenEXR-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.0-12.el8_10.1 | | `OpenEXR-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.0-12.el8_10.1 | | `OpenEXR-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.0-12.el8_10.1 | | `OpenEXR-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.0-12.el8_10.1 | | `OpenEXR-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.2.0-12.el8_10.1 | | `OpenEXR-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.2.0-12.el8_10.1 | | `OpenEXR-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.2.0-12.el8_10.1 | | `OpenEXR-libs-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.2.0-12.el8_10.1 | | `openexr` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.1-3.el9_7.1 | | `openexr-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.1-3.el9_7.1 | | `openexr-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.1-3.el9_7.1 | | `openexr-libs` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.1-3.el9_7.1 | | `openexr-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.1-3.el9_7.1 | | `openexr-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.1.1-3.el9_7.1 | | `openexr-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.1.1-3.el9_7.1 | | `openexr-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.1.1-3.el9_7.1 | | `openexr-libs-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.1.1-3.el9_7.1 | | `openexr` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.1.10-8.el10_0.1 | Products: Openexr Openexr. ## How do I fix CVE-2026-27622? Upgrade openexr to a fixed version for your release line: 3.2.6, 3.3.8 or 3.4.6. ## Is CVE-2026-27622 being exploited? There is no known exploitation of CVE-2026-27622 in the wild and no public exploit code. ## Other vulnerabilities in Openexr Openexr - [CVE-2023-5841](https://insights.sbomify.com/CVE-2023-5841/): OpenEXR Heap Overflow in Scanline Deep Data Parsing (critical 9.1) - [CVE-2026-41142](https://insights.sbomify.com/CVE-2026-41142/): OpenEXR is Vulnerable to Integer overflow in ImageChannel::resize leads to heap OOB write via OpenEXRUtil public API (high 8.8) - [CVE-2026-42216](https://insights.sbomify.com/CVE-2026-42216/): OpenEXR: Out-of-bounds read in `IDManifest::init()` during prefix expansion (high 8.8) - [CVE-2017-9111](https://insights.sbomify.com/CVE-2017-9111/): OpenEXR invalid write (high 8.8) - [CVE-2017-9113](https://insights.sbomify.com/CVE-2017-9113/): Memory corruption in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-27622 and fix it if it is affected. What it is: CVE-2026-27622 is a high-severity vulnerability in Openexr Openexr, published on 3 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-27622 in the wild and no public exploit code. Affected packages and fixed versions: - openexr (PyPI): affected from 2.3.0; fixed in 3.2.6, 3.3.8, 3.4.6 - openexr (PyPI): affected from 2.3.0; fixed in 3.2.6 - openexr (PyPI): affected from 3.3.0; fixed in 3.3.8 - openexr (PyPI): affected from 3.4.0; fixed in 3.4.6 - OpenEXR (PyPI): affected from 2.3.0; fixed in 3.2.6 - OpenEXR (PyPI): affected from 3.3.0; fixed in 3.3.8 - OpenEXR (PyPI): affected from 3.4.0; fixed in 3.4.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-27622/ (Markdown: https://insights.sbomify.com/CVE-2026-27622/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27622 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27622 - OSV: https://osv.dev/vulnerability/CVE-2026-27622 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-27622/ Summaries are generated and may contain mistakes; the official description above is the record.