Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2026-41142

Integer Overflow or Wraparound

Published: May 07, 2026 | Modified: Jul 15, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
8.8 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-41142
CWEhttps://cwe.mitre.org/data/definitions/190.html

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, there is an integer overflow in ImageChannel::resize that leads to heap OOB write via OpenEXRUtil public API. This issue has been patched in versions 3.2.9, 3.3.11, and 3.4.11.

Weakness

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Affected Software

NameVendorStart VersionEnd Version
OpenexrOpenexr3.0.0 (including)3.2.9 (excluding)
OpenexrOpenexr3.3.0 (including)3.3.11 (excluding)
OpenexrOpenexr3.4.0 (including)3.4.11 (excluding)
Red Hat Enterprise Linux 10RedHatopenexr-0:3.1.10-8.el10_2.3*
Red Hat Enterprise Linux 10.0 Extended Update SupportRedHatopenexr-0:3.1.10-8.el10_0.3*
Red Hat Enterprise Linux 9RedHatopenexr-0:3.1.1-3.el9_8.3*
Red Hat Enterprise Linux 9.2 Update Services for SAP SolutionsRedHatopenexr-0:3.1.1-2.el9_2.4*
Red Hat Enterprise Linux 9.4 Update Services for SAP SolutionsRedHatopenexr-0:3.1.1-2.el9_4.4*
Red Hat Enterprise Linux 9.6 Extended Update SupportRedHatopenexr-0:3.1.1-3.el9_6.3*
OpenexrUbuntuesm-infra/xenial*
OpenexrUbuntuquesting*

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
  • Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
  • Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
  • Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
  • Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
  • Understand the programming language’s underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, “not-a-number” calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]
  • Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use