CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NHigh (8.7) in openexr openexr. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in openexr 3.4.8.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Nopenexr (PyPI): fixed in 3.4.8Explain CVE-2026-34543 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34543?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34543?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-34543 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| openexr:openexr | from 3.2.0 before 3.2.7 |
| openexr:openexr | from 3.3.0 before 3.3.9 |
| openexr:openexr | from 3.4.0 before 3.4.8 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-vc68-257w-m432 | PyPI | openexr | >=3.4.0 <3.4.8 | 3.4.8 |
| GHSA-vc68-257w-m432 | PyPI | openexr | >=3.3.0 <=3.3.8 | no fix published |
| GHSA-vc68-257w-m432 | PyPI | openexr | >=3.2.0 <=3.2.6 | no fix published |
| PYSEC-2026-2850 | PyPI | openexr | >=3.2.0 <3.4.8 | 3.4.8 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | openexr | no fix listed | DEBIAN-CVE-2026-34543 |
| Debian | 13 | openexr | 3.2.12-1~deb13u1 | DEBIAN-CVE-2026-34543 |
| Debian | 14 | openexr | 3.4.14-0.1 | DEBIAN-CVE-2026-34543 |
| Ubuntu | 26.10 | openexr | no fix listed | UBUNTU-CVE-2026-34543 |
| openSUSE | Tumbleweed | openexr | 3.4.9-1.1 | openSUSE-SU-2026:10505-1 |
| Alpine | v3.22 | openexr | 3.3.11-r0 | ALPINE-CVE-2026-34543 |
| Alpine | v3.23 | openexr | 3.4.13-r0 | ALPINE-CVE-2026-34543 |
| Alpine | v3.24 | openexr | 3.4.10-r0 | ALPINE-CVE-2026-34543 |
| Alpaquita | stream | openexr | 3.4.8-r0 | BELL-CVE-2026-34543 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine · Alpaquita.
Red Hat rates this Moderate.
Moderate. This information disclosure flaw in OpenEXR allows a remote attacker to leak sensitive heap memory data by tricking a user into opening a specially crafted EXR file. This affects Red Hat Enterprise Linux and Fedora systems that process OpenEXR files.
To mitigate this issue, avoid opening or processing EXR files from untrusted sources. If the OpenEXR library is not essential for system operations, consider removing packages that depend on it to reduce the potential attack surface.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | OpenEXR | Not affected | |
| Red Hat Enterprise Linux 6 | OpenEXR | Out of support scope | |
| Red Hat Enterprise Linux 7 | OpenEXR | Not affected | |
| Red Hat Enterprise Linux 8 | OpenEXR | Not affected | |
| Red Hat Enterprise Linux 9 | OpenEXR | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-34543.