GHSA-66m8-c62j-h6v5 jxl-oxide: `FrameBuffer::new` creates out-of-bounds slices on overflow
An integer overflow in jxl-oxide allows attackers to cause a denial of service via panic on 32-bit platforms.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-66m8-c62j-h6v5?
GHSA-66m8-c62j-h6v5 is a vulnerability in jxl-oxide, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by GHSA-66m8-c62j-h6v5?
2 open source packages ship an affected version, including jxl-oxide.
| Package | Affected | Fixed in |
|---|---|---|
jxl-oxide crates.io | All versions | 0.12.6 |
jxl-oxide crates.io | All versions | 0.12.6 |
How do I fix GHSA-66m8-c62j-h6v5?
Upgrade jxl-oxide to 0.12.6 or later.
Is GHSA-66m8-c62j-h6v5 being exploited?
There is no known exploitation of GHSA-66m8-c62j-h6v5 in the wild and no public exploit code.