openexr — security advisory
OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In versions 3.4.0 through 3.4.11, the HTJ2K (High-Throughput JPEG 2000) decoder, ht_undo_impl() in OpenEXRCore is vulnerable to a heap-buffer-overflow READ. The ht_undo_imp function copies decoded pixels out of a per-line OpenJPH buffer using the EXR channel's declared width as the iteration count. The codestream embedded in the EXR chunk can declare different (smaller) tile/line dimensions than the EXR header advertises, but ht_undo_impl() does not validate this — it pulls width 32-bit samples from cur_line->i32[] without checking the OpenJPH line buffer's actual length. A crafted EXR file produces a 4-byte heap-buffer-overflow READ immediately after a buffer allocated by ojph::local::codestream::finalize_alloc(). The bug is reachable through the standard scanline-decode entry point used by every consumer of exr_decoding_run/Imf::checkOpenEXRFile, including thumbnailers, asset pipelines, and the exrcheck utility — i.e. any application that opens untrusted EXR files. The result is a deterministic crash (DoS) and potential adjacent-heap leak. This issue has been fixed in version 3.4.12.
- Products
- openexr
- Affected versions
- 3.1.13-2, 3.4.6+ds-1, 3.4.6+ds-2, 3.4.6+ds-3, 3.4.6+ds-4
- Fixed versions
- 3.4.14-0.1
- CVEs
- CVE-2026-45696
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 12:16 UTC · Revision 2
Source evidence
OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In versions 3.4.0 through 3.4.11, the HTJ2K (High-Throughput JPEG 2000) decoder, ht_undo_impl() in OpenEXRCore is vulnerable to a heap-buffer-overflow READ. The ht_undo_imp function copies decoded pixels out of a per-line OpenJPH buffer using the EXR channel's declared width as the iteration count. The codestream embedded in the EXR chunk can declare different (smaller) tile/line dimensions than the EXR header advertises, but ht_undo_impl() does not validate this — it pulls width 32-bit samples from cur_line->i32[] without checking the OpenJPH line buffer's actual length. A crafted EXR file produces a 4-byte heap-buffer-overflow READ immediately after a buffer allocated by ojph::local::codestream::finalize_alloc(). The bug is reachable through the standard scanline-decode entry point used by every consumer of exr_decoding_run/Imf::checkOpenEXRFile, including thumbnailers, asset pipelines, and the exrcheck utility — i.e. any application that opens untrusted EXR files. The result is a deterministic crash (DoS) and potential adjacent-heap leak. This issue has been fixed in version 3.4.12.
osv:DEBIAN-CVE-2026-45696
openexr
Fixed versions: 3.4.14-0.1
Complete source record
{
"id": "e901e9ea3aecfc1eb41f6cbdccd438f103ceff7f51e506decfa84a8f0ccb1c47",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2026-45696",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2026-45696",
"summary": "OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In versions 3.4.0 through 3.4.11, the HTJ2K (High-Throughput JPEG 2000) decoder, ht_undo_impl() in OpenEXRCore is vulnerable to a heap-buffer-overflow READ. The ht_undo_imp function copies decoded pixels out of a per-line OpenJPH buffer using the EXR channel's declared width as the iteration count. The codestream embedded in the EXR chunk can declare different (smaller) tile/line dimensions than the EXR header advertises, but ht_undo_impl() does not validate this — it pulls width 32-bit samples from cur_line->i32[] without checking the OpenJPH line buffer's actual length. A crafted EXR file produces a 4-byte heap-buffer-overflow READ immediately after a buffer allocated by ojph::local::codestream::finalize_alloc(). The bug is reachable through the standard scanline-decode entry point used by every consumer of exr_decoding_run/Imf::checkOpenEXRFile, including thumbnailers, asset pipelines, and the exrcheck utility — i.e. any application that opens untrusted EXR files. The result is a deterministic crash (DoS) and potential adjacent-heap leak. This issue has been fixed in version 3.4.12.",
"evidence": "osv:DEBIAN-CVE-2026-45696",
"products": [
{
"name": {
"value": "openexr",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.4.14-0.1",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "3.1.13-2",
"evidence": "/affected/0/versions"
},
{
"value": "3.4.6+ds-1",
"evidence": "/affected/0/versions"
},
{
"value": "3.4.6+ds-2",
"evidence": "/affected/0/versions"
},
{
"value": "3.4.6+ds-3",
"evidence": "/affected/0/versions"
},
{
"value": "3.4.6+ds-4",
"evidence": "/affected/0/versions"
}
]
}
],
"severity": "medium",
"structured": {
"id": "DEBIAN-CVE-2026-45696",
"aliases": [
"DEBIAN-CVE-2026-45696"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "3.4.14-0.1"
}
]
}
],
"package": {
"name": "openexr",
"purl": "pkg:deb/debian/openexr?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"versions": [
"3.1.13-2",
"3.4.6+ds-1",
"3.4.6+ds-2",
"3.4.6+ds-3",
"3.4.6+ds-4"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-45696.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-26T11:47:28.707416058Z",
"provider": "osv",
"upstream": [
"CVE-2026-45696"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2026-45696"
]
},
"related_cves": [
{
"value": "CVE-2026-45696",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 450753,
"published_at": "2026-06-18T21:16:28.917+00:00"
}