CVE-2025-64181

NameCVE-2025-64181
DescriptionOpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In versions 3.3.0 through 3.3.5 and 3.4.0 through 3.4.2, while fuzzing `openexr_exrcheck_fuzzer`, Valgrind reports a conditional branch depending on uninitialized data inside `generic_unpack`. This indicates a use of uninitialized memory. The issue can result in undefined behavior and/or a potential crash/denial of service. Versions 3.3.6 and 3.4.3 fix the issue.
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs1120700

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
openexr (PTS)bookworm3.1.5-5vulnerable
trixie3.1.13-2vulnerable
trixie (security)3.2.12-1~deb13u2vulnerable
forky, sid3.4.16+ds-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
openexrsourcebullseye(not affected)
openexrsource(unstable)3.4.6+ds-11120700

Notes

[trixie] - openexr <no-dsa> (Minor issue)
[bookworm] - openexr <no-dsa> (Minor issue)
[bullseye] - openexr <not-affected> (Vulnerable code not present)
https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-3h9h-qfvw-98hq
Fixed by: https://github.com/AcademySoftwareFoundation/openexr/commit/72aa3e78acfb99eacae8bfae8bf4e4831634db11 (main)
Fixed by: https://github.com/AcademySoftwareFoundation/openexr/commit/df97029a900a2a415fcffbb65ac88bc8972cccfd (v3.4.3-rc)
Fixed by: https://github.com/AcademySoftwareFoundation/openexr/commit/018763e3f52cc8152c1f30bb4a6ec00c6e9b9fb8 (v3.3.6-rc)
Introduced in: https://github.com/AcademySoftwareFoundation/openexr/commit/a04cbf5a48c7a8b6a6dd3b1e2471bde3cd4cb6df (v3.1.0-rc1)
The 3.2.12 Core API still lacks the uncompressed tile packed/unpacked size equality check; the newer C++ reader is not required to reach the affected Core path.

Search for package or bug name: Reporting problems