jxl-oxide: `FrameBuffer::new` creates out-of-bounds slices on overflow
### Summary `jxl-oxide` exposes a public safe API that can construct an undersized `FrameBuffer` due to unchecked `usize` multiplication, which immediately trigger panic while initializing the buffer in normal decoding path. Additionally, calling the safe grouped buffer accessors afterward can create invalid oversized slices from a much smaller allocation, causing undefined behavior; however normal decoding path never reaches UB, because these methods are never used within `jxl-oxide`. ### Impact On 32-bit platforms this can cause panic by accessing out-of-range indices, making it a DoS vulnerability.
AI Analysis
Technical Summary
jxl-oxide's public safe API FrameBuffer::new performs unchecked multiplication of usize values, which can create an undersized FrameBuffer allocation. On 32-bit platforms, this leads to panics when accessing out-of-range indices, causing denial of service. Additionally, safe grouped buffer accessors can create invalid oversized slices from smaller allocations, resulting in undefined behavior, though these accessors are not used in normal decoding paths, preventing exploitation in typical use cases.
Potential Impact
On 32-bit platforms, this vulnerability can cause application panics due to out-of-range index access, resulting in denial of service. There is no impact on confidentiality or integrity, and undefined behavior is theoretically possible but not reached in normal usage.
Mitigation Recommendations
No official patch or fix is currently documented. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using affected versions on 32-bit platforms or in contexts where FrameBuffer::new might be called with unchecked multiplication inputs.
jxl-oxide: `FrameBuffer::new` creates out-of-bounds slices on overflow
Description
### Summary `jxl-oxide` exposes a public safe API that can construct an undersized `FrameBuffer` due to unchecked `usize` multiplication, which immediately trigger panic while initializing the buffer in normal decoding path. Additionally, calling the safe grouped buffer accessors afterward can create invalid oversized slices from a much smaller allocation, causing undefined behavior; however normal decoding path never reaches UB, because these methods are never used within `jxl-oxide`. ### Impact On 32-bit platforms this can cause panic by accessing out-of-range indices, making it a DoS vulnerability.
CVSS v3.1
Score 6.2medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
jxl-oxide's public safe API FrameBuffer::new performs unchecked multiplication of usize values, which can create an undersized FrameBuffer allocation. On 32-bit platforms, this leads to panics when accessing out-of-range indices, causing denial of service. Additionally, safe grouped buffer accessors can create invalid oversized slices from smaller allocations, resulting in undefined behavior, though these accessors are not used in normal decoding paths, preventing exploitation in typical use cases.
Potential Impact
On 32-bit platforms, this vulnerability can cause application panics due to out-of-range index access, resulting in denial of service. There is no impact on confidentiality or integrity, and undefined behavior is theoretically possible but not reached in normal usage.
Mitigation Recommendations
No official patch or fix is currently documented. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using affected versions on 32-bit platforms or in contexts where FrameBuffer::new might be called with unchecked multiplication inputs.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-66m8-c62j-h6v5
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["crates.io"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a46ecb027e9c7971943c47e
Added to database: 07/02/2026, 22:56:48 UTC
Last enriched: 07/02/2026, 23:06:16 UTC
Last updated: 07/31/2026, 12:27:30 UTC
Views: 29
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.
External Links
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.