OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From 3.4.0 to before 3.4.9, a missing bounds check on the dataWindow attribute in EXR file headers allows an attacker to trigger a signed integer overflow in generic_unpack(). By setting dataWindow.min.x to a large negative value, OpenEXRCore computes an enormous image width, which is later used in a signed integer multiplication that overflows, causing the process to terminate with SIGILL via UBSan. This vulnerability is fixed in 3.4.9.

The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1785425808 advisory.

  - OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.4.0 to before 3.4.9, a missing bounds check on the     dataWindow attribute in EXR file headers allows an attacker to trigger a signed integer overflow in     generic_unpack(). By setting dataWindow.min.x to a large negative value, OpenEXRCore computes an enormous     image width, which is later used in a signed integer multiplication that overflows, causing the process to     terminate with SIGILL via UBSan. This vulnerability is fixed in 3.4.9. (CVE-2026-34378)

  - OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a signed integer     overflow exists in undo_pxr24_impl() in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The expression     (uint64_t)(w * 3) computes w * 3 as a signed 32-bit integer before casting to uint64_t. When w is large,     this multiplication constitutes undefined behavior under the C standard. On tested builds (clang/gcc     without sanitizers), two's-complement wraparound commonly occurs, and for specific values of w the wrapped     result is a small positive integer, which may allow the subsequent bounds check to pass incorrectly. If     the check is bypassed, the decoding loop proceeds to write pixel data through dout, potentially extending     far beyond the allocated output buffer. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
    (CVE-2026-34380)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1785425808 advisory.

  - OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.4.0 to before 3.4.9, a missing bounds check on the     dataWindow attribute in EXR file headers allows an attacker to trigger a signed integer overflow in     generic_unpack(). By setting dataWindow.min.x to a large negative value, OpenEXRCore computes an enormous     image width, which is later used in a signed integer multiplication that overflows, causing the process to     terminate with SIGILL via UBSan. This vulnerability is fixed in 3.4.9. (CVE-2026-34378)

  - OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a signed integer     overflow exists in undo_pxr24_impl() in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The expression     (uint64_t)(w * 3) computes w * 3 as a signed 32-bit integer before casting to uint64_t. When w is large,     this multiplication constitutes undefined behavior under the C standard. On tested builds (clang/gcc     without sanitizers), two's-complement wraparound commonly occurs, and for specific values of w the wrapped     result is a small positive integer, which may allow the subsequent bounds check to pass incorrectly. If     the check is bypassed, the decoding loop proceeds to write pixel data through dout, potentially extending     far beyond the allocated output buffer. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
    (CVE-2026-34380)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1785335342 advisory.

  - OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.4.0 to before 3.4.9, a missing bounds check on the     dataWindow attribute in EXR file headers allows an attacker to trigger a signed integer overflow in     generic_unpack(). By setting dataWindow.min.x to a large negative value, OpenEXRCore computes an enormous     image width, which is later used in a signed integer multiplication that overflows, causing the process to     terminate with SIGILL via UBSan. This vulnerability is fixed in 3.4.9. (CVE-2026-34378)

  - OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a signed integer     overflow exists in undo_pxr24_impl() in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The expression     (uint64_t)(w * 3) computes w * 3 as a signed 32-bit integer before casting to uint64_t. When w is large,     this multiplication constitutes undefined behavior under the C standard. On tested builds (clang/gcc     without sanitizers), two's-complement wraparound commonly occurs, and for specific values of w the wrapped     result is a small positive integer, which may allow the subsequent bounds check to pass incorrectly. If     the check is bypassed, the decoding loop proceeds to write pixel data through dout, potentially extending     far beyond the allocated output buffer. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
    (CVE-2026-34380)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1612 advisory.

    OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.4.0 to before 3.4.9, a missing bounds check on the     dataWindow attribute in EXR file headers allows an attacker to trigger a signed integer overflow in     generic_unpack(). By setting dataWindow.min.x to a large negative value, OpenEXRCore computes an enormous     image width, which is later used in a signed integer multiplication that overflows, causing the process to     terminate with SIGILL via UBSan. This vulnerability is fixed in 3.4.9. (CVE-2026-34378)

    OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a signed integer     overflow exists in undo_pxr24_impl() in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The expression     (uint64_t)(w * 3) computes w * 3 as a signed 32-bit integer before casting to uint64_t. When w is large,     this multiplication constitutes undefined behavior under the C standard. On tested builds (clang/gcc     without sanitizers), two's-complement wraparound commonly occurs, and for specific values of w the wrapped     result is a small positive integer, which may allow the subsequent bounds check to pass incorrectly. If     the check is bypassed, the decoding loop proceeds to write pixel data through dout, potentially extending     far beyond the allocated output buffer. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
    (CVE-2026-34380)

    OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.1.0 to before 3.2.7, 3.3.9, and 3.4.9,     internal_exr_undo_piz() advances the working wavelet pointer with signed 32-bit arithmetic. Because nx,     ny, and wcount are int, a crafted EXR file can make this product overflow and wrap. The next channel then     decodes from an incorrect address. The wavelet decode path operates in place, so this yields both out-of-     bounds reads and out-of-bounds writes. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
    (CVE-2026-34588)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 44 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-502486fc61 advisory.

    Backport several OpenEXRCore security fixes

    - Fixes CVE-2026-34378 / GHSA-v76p-4qvv-vh4g; closes RHBZ#2455493
    - Fixes CVE-2026-34380 / GHSA-q3v8-hw4m-59w5; closes RHBZ#2455534
    - Fixes CVE-2026-34588 / GHSA-588r-cr5c-w6hf; closes RHBZ#2455505
    - Fixes CVE-2026-34589 / GHSA-p8xc-w3q4-h64x; closes RHBZ#2455501
    - Fixes CVE-2026-34379 / GHSA-w88v-vqhq-5p24; closes RHBZ#2455497

    ----

    Backport fix for CVE-2026-34544 in OpenEXRCore

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 43 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-cde75a1416 advisory.

    Backport several OpenEXRCore security fixes

    - Fixes CVE-2026-34378 / GHSA-v76p-4qvv-vh4g; closes RHBZ#2455493
    - Fixes CVE-2026-34380 / GHSA-q3v8-hw4m-59w5; closes RHBZ#2455534
    - Fixes CVE-2026-34588 / GHSA-588r-cr5c-w6hf; closes RHBZ#2455505
    - Fixes CVE-2026-34589 / GHSA-p8xc-w3q4-h64x; closes RHBZ#2455501
    - Fixes CVE-2026-34379 / GHSA-w88v-vqhq-5p24; closes RHBZ#2455497

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 45 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-c0f8cde7ad advisory.

    Automatic update for usd-26.03-3.fc45.

    ##### **Changelog**

    ```
    * Wed Apr  8 2026 Benjamin A. Beasley <code@musicinmybrain.net> - 26.03-3
    - Backport several OpenEXRCore security fixes
    - Fixes CVE-2026-34378 / GHSA-v76p-4qvv-vh4g; closes RHBZ#2455493
    - Fixes CVE-2026-34380 / GHSA-q3v8-hw4m-59w5; closes RHBZ#2455534
    - Fixes CVE-2026-34588 / GHSA-588r-cr5c-w6hf; closes RHBZ#2455505
    - Fixes CVE-2026-34589 / GHSA-p8xc-w3q4-h64x; closes RHBZ#2455501
    - Fixes CVE-2026-34379 / GHSA-w88v-vqhq-5p24; closes RHBZ#2455497

    ```

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - OpenEXR provides the specification and reference implementation of the EXR file format, an image storage     format for the motion picture industry. From 3.4.0 to before 3.4.9, a missing bounds check on the     dataWindow attribute in EXR file headers allows an attacker to trigger a signed integer overflow in     generic_unpack(). By setting dataWindow.min.x to a large negative value, OpenEXRCore computes an enormous     image width, which is later used in a signed integer multiplication that overflows, causing the process to     terminate with SIGILL via UBSan. This vulnerability is fixed in 3.4.9. (CVE-2026-34378)

Note that Nessus relies on the presence of the package as reported by the vendor.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the adb096d4-2e72-11f1-acc1-339a1a6999b0 advisory.

    Cary Phillips reports:
    [OpenEXR 3.4.9] addresses the following CVEs:

Tenable has extracted the preceding description block directly from the FreeBSD security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
359749	Rocky Linux 9.6 [TuxCare] Security Update: openexr / openexr-devel / openexr-libs Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1785425808)	Nessus	Rocky Linux Local Security Checks	Local	medium
359574	AlmaLinux 9.6 [TuxCare] Security Update: openexr / openexr-devel / openexr-libs Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1785425808)	Nessus	Alma Linux Local Security Checks	Local	medium
353110	AlmaLinux 9.2 [TuxCare] Security Update: openexr / openexr-devel / openexr-libs Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1785335342)	Nessus	Alma Linux Local Security Checks	Local	medium
311329	Amazon Linux 2023 : openexr, openexr-devel, openexr-libs (ALAS2023-2026-1612)	Nessus	Amazon Linux Local Security Checks	Local	high
310538	Fedora 44 : usd (2026-502486fc61)	Nessus	Fedora Local Security Checks	Local	high
307408	Fedora 43 : usd (2026-cde75a1416)	Nessus	Fedora Local Security Checks	Local	high
305305	Fedora 45 : usd (2026-c0f8cde7ad)	Nessus	Fedora Local Security Checks	Local	high
305086	Linux Distros Unpatched Vulnerability : CVE-2026-34378	Nessus	Misc.	Local	medium
305001	FreeBSD : openexr -- multiple vulnerabilities (adb096d4-2e72-11f1-acc1-339a1a6999b0)	Nessus	FreeBSD Local Security Checks	Local	high

Detections

Analytics

CVE-2026-34378

medium

Tenable Plugins

medium

medium

medium

high

high

high

high

medium

high