jxl-oxide: `FrameBuffer::new` creates out-of-bounds slices on overflow
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### 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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | jxl-oxide (crates.io) | before 0.12.6 | 0.12.6 | Patch available | GHSA-66m8-c62j-h6v5 |
- jxl-oxide (crates.io) Vendor— Affected before 0.12.6 Fixed in 0.12.6 Patch available GHSA-66m8-c62j-h6v5
Remediation
- Fix · GHSA-66m8-c62j-h6v5 jxl-oxide (crates.io) Fixed in 0.12.6 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-66m8-c62j-h6v5
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences