Improper Handling of Length Parameter Inconsistency Affecting OpenEXR package, versions *


Severity

Recommended
0.0
high
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.37% (29th 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-CENTOS6-OPENEXR-17223747
  • published7 Jun 2026
  • disclosed7 May 2026

Introduced: 7 May 2026

CVE-2026-42216  (opens in a new tab)
CWE-130  (opens in a new tab)

How to fix?

There is no fixed version for Centos:6 OpenEXR.

NVD Description

Note: Versions mentioned in the description apply only to the upstream OpenEXR package and not the OpenEXR package as distributed by Centos. See How to fix? for Centos:6 relevant fixed versions and status.

OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From versions 3.0.0 to before 3.2.9, 3.3.0 to before 3.3.11, and 3.4.0 to before 3.4.11, IDManifest::init() reconstructs strings from a prefix-compressed representation. If the previous string is longer than 255 bytes, the next string is expected to begin with a 2-byte prefix length. The code reads stringList[i][0] and stringList[i][1] without checking that the current string has at least two bytes. This issue has been patched in versions 3.2.9, 3.3.11, and 3.4.11.

CVSS Base Scores

version 3.1