Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 07 Apr 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openexr
Openexr openexr |
|
| CPEs | cpe:2.3:a:openexr:openexr:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Openexr
Openexr openexr |
Tue, 07 Apr 2026 07:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Tue, 07 Apr 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Academysoftwarefoundation
Academysoftwarefoundation openexr |
|
| Vendors & Products |
Academysoftwarefoundation
Academysoftwarefoundation openexr |
|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Mon, 06 Apr 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 06 Apr 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From 3.4.0 to before 3.4.9, a missing bounds check on the dataWindow attribute in EXR file headers allows an attacker to trigger a signed integer overflow in generic_unpack(). By setting dataWindow.min.x to a large negative value, OpenEXRCore computes an enormous image width, which is later used in a signed integer multiplication that overflows, causing the process to terminate with SIGILL via UBSan. This vulnerability is fixed in 3.4.9. | |
| Title | OpenEXR has a signed integer overflow in generic_unpack() when parsing EXR files with crafted negative dataWindow.min.x | |
| Weaknesses | CWE-190 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-07T03:07:17.341Z
Reserved: 2026-03-27T13:43:14.370Z
Link: CVE-2026-34378
Updated: 2026-04-06T15:33:03.523Z
Status : Analyzed
Published: 2026-04-06T16:16:35.057
Modified: 2026-04-07T19:05:27.463
Link: CVE-2026-34378
OpenCVE Enrichment
Updated: 2026-04-08T19:50:47Z