Vulnerability · CVE-2026-39886
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry.
Published Apr 21, 2026 · catalog updated Jun 17, 2026 · OpenEXR provides the specification
Check if you run it
No confirmed exploitation is on record for CVE-2026-39886. EPSS is 0.43%. Act only if a listed version of OpenEXR provides the specification is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (OpenEXR provides the specification).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.43%
- Remediation
- Advisory link
- Affected products
- cpe openexr/openexr
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. Versions 3.4.0 through 3.4.9 have a signed integer overflow vulnerability in OpenEXR's HTJ2K (High-Throughput JPEG 2000) decompression path. The function in accumulates a bytes-per-line value ( ) using a 32-bit signed integer with no overflow guard. A crafted EXR file with 16,385 FLOAT channels at the HTJ2K maximum width of 32,767 causes to overflow , producing undefined behavior confirmed by UBSan. On an allocator-permissive host where the required ~64 GB allocation succeeds, the wrapped negative value would subsequently be used as a per-scanline pointer advance, which would produce a heap out-of-bounds write. On a memory-constrained host, the allocation fails before is entered. This is the second distinct integer overflow in . CVE-2026-34545 addressed a different overflow in the same function — the pixel-loop counter at line ~302 that overflows when iterating over channels whose exceeds 32,767. The CVE-2026-34545 fix did not touch the accumulator at line 211, which is the subject of this advisory. The accumulator was also not addressed by any of the 8 advisories in the 2026-04-05 v3.4.9 release batch. This finding is structurally identical to CVE-2026-34588 (PIZ overflow in ) and should be remediated with the same pattern. The CVE-2026-34588 fix did not touch . Version 3.4.10 contains a remediation that addresses the vulnerability in .
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe openexr/openexrversion unspecified
How to fix CVE-2026-39886
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-39886. EPSS is 0.43%. Act only if a listed version of OpenEXR provides the specification is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-190: Integer Overflow. EPSS 0.43%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Apr 21, 2026 · NIST NVD
Detected
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. Versions 3.4.0 through 3.4.9 have a signed integer overflow vulnerability in OpenEXR's HTJ2K (High-Throughput JPEG 2000) decompression path. The function in accumulates a bytes-per-line value ( ) using a 32-bit signed integer with no overflow guard. A cra
Jun 17, 2026 · NIST NVD
Updated
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. Versions 3.4.0 through 3.4.9 have a signed integer overflow vulnerability in OpenEXR's HTJ2K (High-Throughput JPEG 2000) decompression path. The function in accumulates a bytes-per-line value ( ) using a 32-bit signed integer with no overflow guard. A cra
Sources
- CVE.orgVulnerability recordCVE-2026-39886
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-39886
30-day exploitation probability 0.4%
first.org - NIST NVDVulnerability recordCVE-2026-39886
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. Versions 3.4.0 through 3.4.9 have a signed integer overflow vulnerability in OpenEXR's HTJ2K (High-Throughput JPEG 2000) decompression
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.