CVE-2026-34544

| EUVD-2026-18060 HIGH
2026-04-01 GitHub_M GHSA-h762-rhv3-h25v
8.4
CVSS 4.0
Share

CVSS Vector

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/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
Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
A
Scope
X

Lifecycle Timeline

4
Patch Released
Apr 04, 2026 - 02:30 nvd
Patch available
Analysis Generated
Apr 01, 2026 - 21:15 vuln.today
EUVD ID Assigned
Apr 01, 2026 - 21:15 euvd
EUVD-2026-18060
CVE Published
Apr 01, 2026 - 20:55 nvd
HIGH 8.4

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, a crafted B44 or B44A EXR file can cause an out-of-bounds write in any application that decodes it via exr_decoding_run(). Consequences range from immediate crash (most likely) to corruption of adjacent heap allocations (layout-dependent). This issue has been patched in version 3.4.8.

Analysis

Out-of-bounds heap write in OpenEXR 3.4.0-3.4.7 allows local attackers to crash applications or corrupt memory when processing malicious B44/B44A compressed EXR files. Attack requires user interaction to open a crafted image file. …

Sign in for full analysis, threat intelligence, and remediation guidance.

Remediation

Within 24 hours: inventory all systems and applications using OpenEXR 3.4.0-3.4.7 and disable EXR file ingestion or restrict to trusted sources only. Within 7 days: upgrade to OpenEXR 3.4.8 or later where available, or implement strict file validation and sandboxing for EXR processing. …

Sign in for detailed remediation steps.

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: +0.0
CVSS: +42
POC: 0

Share

CVE-2026-34544 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy