CVE-2026-42216
CRITICALDescription
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From versions 3.0.0 to before 3.2.9, 3.3.0 to before 3.3.11, and 3.4.0 to before 3.4.11, IDManifest::init() reconstructs strings from a prefix-compressed representation. If the previous string is longer than 255 bytes, the next string is expected to begin with a 2-byte prefix length. The code reads stringList[i][0] and stringList[i][1] without checking that the current string has at least two bytes. This issue has been patched in versions 3.2.9, 3.3.11, and 3.4.11.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 38% of all known CVEs.
References
Related Vulnerabilities
Other CWE-125 (Out-of-bounds Read) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2014-0160 | High | 7.5 | 100% | KEV | Fix |
| CVE-2025-5777 | High | 7.5 | 100% | KEV + Ransom | Fix |
| CVE-2021-4034 | High | 7.8 | 95% | KEV | Fix |
| CVE-2020-8794 | Critical | 9.8 | 89% | - | Fix |
| CVE-2023-49285 | High | 8.6 | 89% | - | Fix |
| CVE-2023-21769 | High | 7.5 | 89% | - | Fix |
Common questions
How do I fix CVE-2026-42216?
Published advisories record a fix for 12 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-42216 being actively exploited?
Not that we know of. CVE-2026-42216 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.46% is the estimated probability that it will be exploited in the next 30 days. That is higher than 38% of all scored CVEs.
How severe is CVE-2026-42216?
CVE-2026-42216 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-42216 affect?
Published advisories record a fix for openexr (Rocky), openexr (Red Hat / RHEL), openexr-debuginfo (Red Hat / RHEL), openexr-debuginfo (Rocky), and 8 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-42216
Markdown
[](https://tridentstack.com/cve/CVE-2026-42216)HTML
<a href="https://tridentstack.com/cve/CVE-2026-42216"><img src="https://tridentstack.com/cve/badge/CVE-2026-42216.svg" alt="CVE-2026-42216"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-15.