CVE-2026-59983: OpenEXR security update
Affects OpenEXRSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.5 Medium : upgrade to 3.1.11-10.oe2403sp1 when convenient.
Data as of 4 Nov 2026, 17:00 UTC
- Patch
- Available – fixed in 3.1.11-10.oe2403sp1
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade OpenEXR to 3.1.11-10.oe2403sp1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
openEuler 24.03-LTS-SP1OpenEXRpkg:rpm/openEuler/OpenEXR&distro=openEuler-24.03-LTS-SP1Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and should be applied by upgrading OpenEXR to versions 3.2.11, 3.3.13, or 3.4.14, which address these vulnerabilities. Users should avoid processing untrusted EXR files with vulnerable versions until patched. No other specific mitigations are indicated by the vendor advisory.
Description
OpenEXR, a widely used HDR image file format implementation, has multiple vulnerabilities affecting versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 on ILP32 builds. These include an out-of-bounds read triggered by crafted uncompressed deep-tile EXR files causing denial of service, and a heap out-of-bounds write in the exrmultiview utility when combining two crafted scanline EXR files with misaligned union dataWindows. Both issues are fixed in versions 3.2.11, 3.3.13, and 3.4.14.