Skip to main content
Public proof of conceptFix available

CVE-2026-34543

A public proof of concept exists; no exploitation attested.

  • Published2026-04-01
  • Fixed in3.4.8 · 3.3.9 · 3.2.7
  • WeaknessCWE-908

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From version 3.4.0 to before version 3.4.8, sensitive information from heap memory may be leaked through the decoded pixel data (information disclosure). This occurs under default settings; simply reading a malicious EXR file is sufficient to trigger the issue, without any user interaction. This issue has been patched in version 3.4.8.

Timeline

dates in UTC
  1. 2026-04-0121:17CVE publishedNVD

Versions per branch

NVD · OSV
Openexr
BranchAffectedFixed in
3.4≥ 3.4.0, < 3.4.83.4.8
3.x≥ 3.2.0, < 3.4.83.4.8
3.3≥ 3.3.0, < 3.3.93.3.9
3.2≥ 3.2.0, < 3.2.73.2.7
3.2≥ 3.2.0, ≤ 3.2.6no fix published
3.3≥ 3.3.0, ≤ 3.3.8no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • AcademySoftwareFoundation openexr
    Affected
    • = >= 3.4.0, < 3.4.8no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-04-01

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • openexrWolfiall versions · fixed in 3.4.9-r0and 7 other packages
  • openexrUbuntu:26.10all versions · no fixed version listed
  • openexrRoot:Debian:13all versions · fixed in 3.1.13-2.aikido.14and 1 other package
  • openexrRoot:Debian:13all versions · fixed in 3.1.13-2.aikido.15and 1 other package
  • openexrRoot:Debian:13all versions · fixed in 3.1.13-2.root.io.12and 1 other package
  • openexrRoot:Debian:13all versions · fixed in 3.1.13-2.root.io.13and 1 other package
  • openexrRoot:Debian:12all versions · fixed in 3.1.5-5.root.io.15and 1 other package
  • openexrRoot:Debian:12all versions · fixed in 3.1.5-5.aikido.24and 1 other package

22 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Openexr to 3.4.8 · 3.3.9 · 3.2.7

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-04-01
Last Modified
2026-10-26
NVD status
Analyzed
GitHub Advisory
GHSA-vc68-257w-m432

Frequently asked questions

What is CVE-2026-34543?

OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From version 3.4.0 to before version 3.4.8, sensitive information from heap memory may be leaked through the decoded pixel data (information disclosure). This occurs under default settings; simply reading a malicious EXR file is sufficient to trigger the issue, without any user interaction. This issue has been patched in version 3.4.8.

Is CVE-2026-34543 actively exploited?

A proof-of-concept exploit exists for CVE-2026-34543, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-34543?

CVE-2026-34543 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running openexr? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record