# 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.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jul 2026

## 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 | Ecosystem | 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.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-66m8-c62j-h6v5 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of GHSA-66m8-c62j-h6v5 in the wild and no public exploit code.

Affected packages and fixed versions:
- jxl-oxide (crates.io): affected all versions; fixed in 0.12.6
- jxl-oxide (crates.io): affected all versions; fixed in 0.12.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-66m8-c62j-h6v5/ (Markdown: https://insights.sbomify.com/GHSA-66m8-c62j-h6v5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-66m8-c62j-h6v5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-66m8-c62j-h6v5/
Summaries are generated and may contain mistakes; the official description above is the record.