CVE-2026-34379: CWE-704: Incorrect Type Conversion or Cast in AcademySoftwareFoundation openexr
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a misaligned memory write vulnerability exists in LossyDctDecoder_execute() in src/lib/OpenEXRCore/internal_dwa_decoder.h:749. When decoding a DWA or DWAB-compressed EXR file containing a FLOAT-type channel, the decoder performs an in-place HALF→FLOAT conversion by casting an unaligned uint8_t * row pointer to float * and writing through it. Because the row buffer may not be 4-byte aligned, this constitutes undefined behavior under the C standard and crashes immediately on architectures that enforce alignment (ARM, RISC-V, etc.). On x86 it is silently tolerated at runtime but remains exploitable via compiler optimizations that assume aligned access. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
AI Analysis
Technical Summary
The vulnerability arises from incorrect type conversion and casting in the openexr library's LossyDctDecoder_execute() function. Specifically, when decoding certain compressed EXR image files, the code casts an unaligned uint8_t pointer to a float pointer and writes through it, violating alignment requirements. This leads to undefined behavior, immediate crashes on some CPU architectures, and potential exploitation on others due to compiler optimizations. The issue affects openexr versions >=3.2.0 and <3.2.7, >=3.3.0 and <3.3.9, and >=3.4.0 and <3.4.9. The vendor has fixed the vulnerability in versions 3.2.7, 3.3.9, and 3.4.9.
Potential Impact
This vulnerability can cause application crashes on architectures that enforce strict memory alignment, such as ARM and RISC-V, leading to denial of service. On x86 architectures, the undefined behavior may be exploited due to compiler optimizations assuming aligned memory access, potentially leading to memory corruption or other unintended behavior. The CVSS score of 7.1 reflects a high severity with network attack vector, low attack complexity, no privileges required, user interaction needed, unchanged scope, no confidentiality impact, low integrity impact, and high availability impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix is available and has been released in openexr versions 3.2.7, 3.3.9, and 3.4.9. Users and organizations should upgrade to one of these fixed versions to remediate the vulnerability. Patch status is confirmed by the vendor's versioning information. No additional mitigation steps are indicated by the vendor advisory.
CVE-2026-34379: CWE-704: Incorrect Type Conversion or Cast in AcademySoftwareFoundation openexr
Description
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a misaligned memory write vulnerability exists in LossyDctDecoder_execute() in src/lib/OpenEXRCore/internal_dwa_decoder.h:749. When decoding a DWA or DWAB-compressed EXR file containing a FLOAT-type channel, the decoder performs an in-place HALF→FLOAT conversion by casting an unaligned uint8_t * row pointer to float * and writing through it. Because the row buffer may not be 4-byte aligned, this constitutes undefined behavior under the C standard and crashes immediately on architectures that enforce alignment (ARM, RISC-V, etc.). On x86 it is silently tolerated at runtime but remains exploitable via compiler optimizations that assume aligned access. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from incorrect type conversion and casting in the openexr library's LossyDctDecoder_execute() function. Specifically, when decoding certain compressed EXR image files, the code casts an unaligned uint8_t pointer to a float pointer and writes through it, violating alignment requirements. This leads to undefined behavior, immediate crashes on some CPU architectures, and potential exploitation on others due to compiler optimizations. The issue affects openexr versions >=3.2.0 and <3.2.7, >=3.3.0 and <3.3.9, and >=3.4.0 and <3.4.9. The vendor has fixed the vulnerability in versions 3.2.7, 3.3.9, and 3.4.9.
Potential Impact
This vulnerability can cause application crashes on architectures that enforce strict memory alignment, such as ARM and RISC-V, leading to denial of service. On x86 architectures, the undefined behavior may be exploited due to compiler optimizations assuming aligned memory access, potentially leading to memory corruption or other unintended behavior. The CVSS score of 7.1 reflects a high severity with network attack vector, low attack complexity, no privileges required, user interaction needed, unchanged scope, no confidentiality impact, low integrity impact, and high availability impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix is available and has been released in openexr versions 3.2.7, 3.3.9, and 3.4.9. Users and organizations should upgrade to one of these fixed versions to remediate the vulnerability. Patch status is confirmed by the vendor's versioning information. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-27T13:43:14.370Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d3d1a00a160ebd92c130df
Added to database: 4/6/2026, 3:30:40 PM
Last enriched: 4/6/2026, 3:45:30 PM
Last updated: 5/21/2026, 10:26:47 PM
Views: 73
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.