OpenEXR is the reference implementation and specification for the EXR image file format, widely used in the motion picture industry. In versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13, the PyOpenEXR Python bindings return stale heap data when reading a crafted deep scanline EXR that uses layer-prefixed RGB channels. With the default channel coalescing (separate_channels=False), the wrapper groups channels such as left.R, left.G, and left.B into a single RGB sample array, but the lane-offset calculation in PyPart::setDeepSliceData() only recognizes the exact unprefixed names G, B, and A. As a result, prefixed channels like left.G and left.B are decoded into lane 0 while lanes 1 and 2 are left uninitialized and returned to Python. A Python application that reads untrusted deep EXR files through the default OpenEXR.File API and then logs, serializes, previews, or otherwise processes the resulting NumPy sample arrays may expose uninitialized same-process heap contents, in addition to receiving incorrect green and blue channel data. This issue is fixed in versions 3.3.13 and 3.4.14.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - OpenEXR is the reference implementation and specification for the EXR image file format, widely used in     the motion picture industry. In versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13, the PyOpenEXR     Python bindings return stale heap data when reading a crafted deep scanline EXR that uses layer-prefixed     RGB channels. With the default channel coalescing (separate_channels=False), the wrapper groups channels     such as left.R, left.G, and left.B into a single RGB sample array, but the lane-offset calculation in     PyPart::setDeepSliceData() only recognizes the exact unprefixed names G, B, and A. As a result, prefixed     channels like left.G and left.B are decoded into lane 0 while lanes 1 and 2 are left uninitialized and     returned to Python. A Python application that reads untrusted deep EXR files through the default     OpenEXR.File API and then logs, serializes, previews, or otherwise processes the resulting NumPy sample     arrays may expose uninitialized same-process heap contents, in addition to receiving incorrect green and     blue channel data. This issue is fixed in versions 3.3.13 and 3.4.14. (CVE-2026-62986)

Note that Nessus relies on the presence of the package as reported by the vendor.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 56449320-97c5-11f1-84d7-3c7c3fba4204 advisory.

    Cary Phillips reports:
    [The OpenEXR 3.4.14] release addresses the following security vulnerabilities:

Tenable has extracted the preceding description block directly from the FreeBSD security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
339682	Linux Distros Unpatched Vulnerability : CVE-2026-62986	Nessus	Misc.	Local	medium
335504	FreeBSD : OpenEXR -- 3.4.14 fixes multiple vulnerabilities (56449320-97c5-11f1-84d7-3c7c3fba4204)	Nessus	FreeBSD Local Security Checks	Local	high

Detections

Analytics

CVE-2026-62986

medium

Tenable Plugins

medium

high