PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-59982 AcademySoftwareFoundation CVE debrief

CVE-2026-59982 is a vulnerability in OpenEXR, a widely used image format in the motion picture industry. A crafted deep EXR image can cause an out-of-bounds pointer return, potentially leading to a crash or limited information disclosure. The issue is fixed in OpenEXR versions 3.2.11, 3.3.13, and 3.4.14. This vulnerability affects systems and applications using OpenEXR, particularly in the motion picture industry, and defenders should assess exposure and prioritize updates to prevent potential crashes or information disclosure.

Vendor
AcademySoftwareFoundation
Product
openexr
CVSS
HIGH 7.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-25
Original CVE updated
2026-09-09
Advisory published
2026-08-25
Advisory updated
2026-09-09

Who should care

Defenders responsible for systems and applications using OpenEXR should assess exposure and prioritize updates to prevent potential crashes or information disclosure. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and update affected systems and applications.

Why it matters

CVE-2026-59982 is a vulnerability in OpenEXR that can cause system crashes or limited information disclosure. Defenders should prioritize updates to prevent these consequences.

  • Potential system crashes due to out-of-bounds pointer returns
  • Limited information disclosure from crafted deep EXR images

Technical summary

OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 can return an out-of-bounds pointer from TypedDeepImageChannel::row() when a crafted deep EXR has a nonzero dataWindow origin. This vulnerability occurs because the API combines zero-based row access with an absolute-coordinate-adjusted base pointer, allowing a crash or limited information disclosure. The issue has been fixed in OpenEXR versions 3.2.11, 3.3.13, and 3.4.14, and defenders should prioritize updating OpenEXR to a fixed version.

Defensive priority

Defenders should prioritize updating OpenEXR to a fixed version to prevent potential crashes or information disclosure.

Recommended defensive actions

  • Update OpenEXR to version 3.2.11, 3.3.13, or 3.4.14
  • Review and update affected systems and applications
  • Monitor for potential crashes or information disclosure
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and affected versions. The vulnerability has been fixed in OpenEXR versions 3.2.11, 3.3.13, and 3.4.14. Defenders should verify affected scope, severity, and vendor guidance. The CVE record was published on 2026-08-25T18:17:56.747Z and has not been modified since then.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-59982 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-59982

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-59982 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-59982

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.