CVE-2026-42217: OpenEXR: Shift exponent overflow in `readVariableLengthInteger()` (`ImfIDManifest.cpp`)

Published May 7, 2026
·
Updated

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, readVariableLengthInteger() decodes a variable-length integer from untrusted EXR input without bounding the shift count. After enough continuation bytes, the code executes a left shift by 70 on a 64-bit value, which is undefined behavior. This issue has been patched in versions 3.2.9, 3.3.11, and 3.4.11.

Affected Software

4 affected components
OpenEXR OpenEXR>=3.0.0<3.2.9, >=3.3.0<3.3.11, >=3.4.0<3.4.11
OpenEXR OpenEXR>=3.0.0<3.2.9
OpenEXR OpenEXR>=3.3.0<3.3.11
OpenEXR OpenEXR>=3.4.0<3.4.11

Event History

May 7, 2026
CVE Published
via MITRE·04:04 AM
Data Sourced
via MITRE·04:04 AM
DescriptionWeakness
Data Sourced
via NVD·04:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-42217?

CVE-2026-42217 is classified as a high severity vulnerability due to the potential for exploitation leading to denial of service or unintended behavior.

2

How do I fix CVE-2026-42217?

To remediate CVE-2026-42217, users should upgrade to versions of OpenEXR that are not affected, specifically version 3.2.9 or later, 3.3.11 or later, or 3.4.11 or later.

3

What versions are affected by CVE-2026-42217?

CVE-2026-42217 affects OpenEXR versions from 3.0.0 to before 3.2.9, and from 3.3.0 to before 3.3.11, as well as from 3.4.0 to before 3.4.11.

4

What is the impact of CVE-2026-42217?

The impact of CVE-2026-42217 includes potential overflow issues that can lead to application crashes or security vulnerabilities in the handling of EXR files.

5

Who is responsible for fixing CVE-2026-42217?

The responsibility for fixing CVE-2026-42217 falls on developers and users of OpenEXR to update to the patched versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203