Bug 2537147 - CVE-2026-59981 openexr: OpenEXR: Information disclosure and denial of service via out-of-bounds read [fedora-all]
Summary: CVE-2026-59981 openexr: OpenEXR: Information disclosure and denial of service...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: openexr
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Richard Shaw
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["55b67b4a-2bc6-481b-8e05-5...
Depends On:
Blocks: CVE-2026-59981
TreeView+ depends on / blocked
 
Reported: 2026-09-19 11:34 UTC by Vladimir Vasilev
Modified: 2026-09-19 11:34 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-09-19 11:34:11 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.


Note You need to log in before you can comment on or make changes to this bug.