Out-of-bounds Write Affecting openexr-devel package, versions <2.2.1-150000.3.52.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.15% (4th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES157-OPENEXRDEVEL-18200232
  • published22 Jul 2026
  • disclosed21 Jul 2026

Introduced: 21 Jul 2026

CVE-2026-55059  (opens in a new tab)
CWE-787  (opens in a new tab)

How to fix?

Upgrade SLES:15.7 openexr-devel to version 2.2.1-150000.3.52.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openexr-devel package and not the openexr-devel package as distributed by SLES. See How to fix? for SLES:15.7 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1