OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 are vulnerable to crashing. This occurs when Imf::GetChannelsInMultiPartFile() processes a crafted EXR with an empty multiView header attribute and Imf::viewFromChannelName() indexes the empty vector for a dotless channel name. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - OpenEXR is the reference implementation and specification for the EXR image format, widely used in the
    motion picture industry. OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13
    are vulnerable to crashing. This occurs when Imf::GetChannelsInMultiPartFile() processes a crafted EXR
    with an empty multiView header attribute and Imf::viewFromChannelName() indexes the empty vector for a
    dotless channel name. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14. (CVE-2026-61555)

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:4003-1 advisory.

    - CVE-2026-59184: invalid heap pointer, causing out-of-bounds or use-after-free writes (bsc#1276849).
    - CVE-2026-59186: On ILP32, the Array2D<Rgba> tile-conversion buffer size calculation overflows, allocates     a much       smaller heap buffer, and tile decode writes past that allocation (bsc#1276850).
    - CVE-2026-59189: API can return an out-of-bounds pointer when a deep image has a non-zero dataWindow     origin, resulting       in a heap out-of-bounds read and crash, with potential information disclosure under a controlled heap     layout       (bsc#1276855).
    - CVE-2026-59981: an attacker-controlled deep EXR file can access sample counts through row() performs an     out-of-bounds       read, which can crash the process or, under a controlled heap layout, return adjacent heap memory as     sample-count       values (bsc#1276862).
    - CVE-2026-59982: an out-of-bounds pointer from TypedDeepImageChannel::row() when a crafted deep EXR has a     nonzero       dataWindow origin (bsc#1276853).
    - CVE-2026-61555: crashing occurs when Imf::GetChannelsInMultiPartFile() processes a crafted EXR with an     empty multiView       header attribute and Imf::viewFromChannelName() indexes the empty vector for a dotless channel name     (bsc#1276859).
    - CVE-2026-68515: The utility allocates sampled channel storage using a truncated union_width / xSampling,     then reads       the sampled input through a Slice based on the misaligned union window, producing a heap out-of-bounds     write       (bsc#1276848).

Tenable has extracted the preceding description block directly from the SUSE 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 SUSE Linux SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:4005-1 advisory.

    - CVE-2026-59186: On ILP32, the Array2D<Rgba> tile-conversion buffer size calculation overflows, allocates     a much       smaller heap buffer, and tile decode writes past that allocation (bsc#1276850).
    - CVE-2026-61555: crashing occurs when Imf::GetChannelsInMultiPartFile() processes a crafted EXR with an     empty multiView       header attribute and Imf::viewFromChannelName() indexes the empty vector for a dotless channel name     (bsc#1276859).
    - CVE-2026-68515: The utility allocates sampled channel storage using a truncated union_width / xSampling,     then reads       the sampled input through a Slice based on the misaligned union window, producing a heap out-of-bounds     write       (bsc#1276848).

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

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-2154 advisory.

    OpenEXR is the reference implementation and specification for the EXR image format, widely used in the     motion picture industry. Versions prior to 3.2.10, 3.3.12 and 3.4.13 contain a heap out-of-bounds write in     Imf_4_0::SampleCountChannel::set(int r, unsigned int newNumSamples[]). The row-based sample-count setter     computes the target Y coordinate with dataWindow.min.x instead of dataWindow.min.y. For a valid deep image     data window where min.x != min.y, a valid row index can be translated into an invalid Y coordinate,     causing writes before the allocated _numSamples buffer. The vulnerability is reachable through the public     OpenEXRUtil DeepImage API and can lead to heap corruption and process crashes. This issue has been fixed     in versions 3.2.10, 3.3.12 and 3.4.13. (CVE-2026-55059)

    OpenEXR is the reference implementation and specification for the EXR image format, widely used in the     motion picture industry. Versions prior to 3.2.10, 3.3.12, and 3.4.13 contain an infinite-loop     vulnerability in SampleCountChannel. The helper roundListSizeUp() rounds a sample-list size up to the next     power of two using repeated unsigned left shifts, which terminates for normal values but fails for     UINT_MAX: the sequence reaches 0x80000000, and the next left shift wraps the 32-bit value to 0. Because 0     remains less than UINT_MAX, the loop never progresses and never exits. The bug is reachable through public     OpenEXRUtil APIs, either by editing the sample-count buffer through SampleCountChannel::Edit (whose     destructor calls endEdit()) or by calling SampleCountChannel::set(x, y, UINT_MAX) on a valid pixel. This     issue has been fixed in versions 3.2.10, 3.3.12, and 3.4.13. (CVE-2026-55373)

    OpenEXR is the reference implementation and specification for the EXR image format, widely used in the     motion picture industry. In versions 3.1.0 through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13,     an int32_t multiplication in OpenEXRCore's unpack_sample_table() can overflow while decoding a crafted     deep tiled EXR file, producing an invalid pointer that leads to a read from an unmapped memory address and     a crash. Because the overflow occurs in the standard decoding path (exr_decoding_run), any application     that decodes deep tiled EXR files is affected. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.
    (CVE-2026-59183)

    OpenEXR is the reference implementation and specification for the EXR image format, widely used in the     motion picture industry. Versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 allow a     crafted EXR with a nonzero dataWindow.min to make TypedFlatImageChannel::row() return an invalid heap     pointer, causing out-of-bounds or use-after-free writes. This occurs when an application writes rows     through FlatHalfChannel::row(). Affected consumers are tools, converters, render pipeline components, or     image-processing services that accept untrusted EXR files and use FlatHalfChannel::row() on loaded images.
    This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14. (CVE-2026-59184)

    OpenEXR is the reference implementation and specification for the EXR image format, widely used in the     motion picture industry. In OpenEXRUtil versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.12, the     documented TypedDeepImageChannel<T>::row() API can return an out-of-bounds pointer when a deep image has a     non-zero dataWindow origin, resulting in a heap out-of-bounds read and crash, with potential information     disclosure under a controlled heap layout. The flaw arises because ImfDeepImageChannel uses two     conflicting coordinate models: at(x, y) uses absolute coordinates (with _base offset by dataWindow.min),     while row(r) is documented as 0-based logical access. For a non-zero dataWindow.min, row(0) therefore     points outside the _sampleListPointers allocation instead of at the first logical row. This issue is fixed     in versions 3.3.13 and 3.4.13. (CVE-2026-59189)

    OpenEXR is the reference implementation and specification for the EXR image file format, widely used in     the motion picture industry. In versions through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13,     the OpenEXRUtil library returns an out-of-bounds pointer from the SampleCountChannel::row() API when a     deep image has a non-zero dataWindow origin. The row() accessor is documented as 0-based and computes its     address from an internal base that is offset for absolute pixel coordinates, so the two coordinate models     conflict whenever dataWindow.min is non-zero. For a deep image whose data window has a large negative     vertical origin, row(0) points far outside the allocated sample-count buffer. An application that opens an     attacker-controlled deep EXR file and accesses sample counts through row() performs an out-of-bounds read,     which can crash the process or, under a controlled heap layout, return adjacent heap memory as sample-     count values. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14. (CVE-2026-59981)

    OpenEXR is the reference implementation and specification for the EXR image format, widely used in the     motion picture industry. OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13     can return an out-of-bounds pointer from TypedDeepImageChannel::row() when a crafted deep EXR has a     nonzero dataWindow origin. This vulnerability occurs because the API combines zero-based row access with     an absolute-coordinate-adjusted base pointer, allowing a crash or limited information disclosure. This     issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14. (CVE-2026-59982)

    OpenEXR is the reference implementation and specification for the EXR image format, widely used in the     motion picture industry. OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13     are vulnerable to crashing. This occurs when Imf::GetChannelsInMultiPartFile() processes a crafted EXR     with an empty multiView header attribute and Imf::viewFromChannelName() indexes the empty vector for a     dotless channel name. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14. (CVE-2026-61555)

    OpenEXR is the reference implementation and specification for the EXR image format, widely used in the     motion picture industry. In versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13,     exrmultiview can write past a heap allocation when it combines two attacker-supplied, individually valid     scanline EXR files whose union dataWindow is not aligned to one view's channel subsampling. The utility     allocates sampled channel storage using a truncated union_width / xSampling, then reads the sampled input     through a Slice based on the misaligned union window, producing a heap out-of-bounds write. The trigger is     normal public-tool processing, such as exrmultiview left A.exr right B.exr out.exr with crafted but valid     inputs, so this is not solely an API or caller-precondition issue. This issue is fixed in versions 3.2.11,     3.3.13, and 3.4.14. (CVE-2026-68515)

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - OpenEXR is the reference implementation and specification for the EXR image format, widely used in the     motion picture industry. OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13     are vulnerable to crashing. This occurs when Imf::GetChannelsInMultiPartFile() processes a crafted EXR     with an empty multiView header attribute and Imf::viewFromChannelName() indexes the empty vector for a     dotless channel name. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14. (CVE-2026-61555)

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 56449320-97c5-11f1-84d7-3c7c3fba4204 advisory.

    Cary Phillips reports:
    [The OpenEXR 3.4.14] release addresses the following security vulnerabilities:

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
461091	Echo: openexr: security update to 3.1.13-2+e3	Tenable Cloud Security	Echo Local Security Checks	Local	medium
461091	Echo: openexr: security update to 3.1.13-2+e3	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	medium
348450	SUSE SLED15 / SLES15 Security Update : openexr (SUSE-SU-2026:4003-1)	Nessus	SuSE Local Security Checks	Local	high
348449	SUSE SLES12 Security Update : openexr (SUSE-SU-2026:4005-1)	Nessus	SuSE Local Security Checks	Local	high
345802	Amazon Linux 2023 : openexr, openexr-devel, openexr-libs (ALAS2023-2026-2154)	Nessus	Amazon Linux Local Security Checks	Local	high
339671	Linux Distros Unpatched Vulnerability : CVE-2026-61555	Nessus	Misc.	Local	medium
335504	FreeBSD : OpenEXR -- 3.4.14 fixes multiple vulnerabilities (56449320-97c5-11f1-84d7-3c7c3fba4204)	Nessus	FreeBSD Local Security Checks	Local	high

Detections

Analytics

CVE-2026-61555

medium

Tenable Plugins

medium

medium

high

high

high

medium

high