# GHSA-2v8p-fqpx-2q3w: jxl-oxide: integer subtraction overflow panic in cluster_from_table via crafted JXL input (DoS)

> Crafted JXL images cause a panic in jxl-oxide when overflow checks are enabled, leading to denial of service in applications processing untrusted images.

- **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-2v8p-fqpx-2q3w?

GHSA-2v8p-fqpx-2q3w is a vulnerability in jxl-modular, 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
Logic bug in `decode_simple_table_slow` may cause integer arithmetic overflow when decoding Modular image with certain kind of MA tree, which may panic with `overflow-checks` enabled.

### Impact
Denial of service: any application passing untrusted JXL data to `JxlImage::render_frame` (or equivalent) can be
crashed. Affects all builds with overflow checks enabled, which includes debug builds and any release build
that sets `overflow-checks = true` in Cargo.toml or `[profile.*]`.

No memory corruption is possible — the panic fires before any unsafe code is reached.

## Which versions are affected by GHSA-2v8p-fqpx-2q3w?

2 open source packages ship an affected version, including jxl-modular.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jxl-modular` | crates.io | All versions | 0.11.3 |
| `jxl-modular` | crates.io | All versions | 0.11.3 |

## How do I fix GHSA-2v8p-fqpx-2q3w?

Upgrade jxl-modular to 0.11.3 or later.

## Is GHSA-2v8p-fqpx-2q3w being exploited?

There is no known exploitation of GHSA-2v8p-fqpx-2q3w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2v8p-fqpx-2q3w and fix it if it is affected.

What it is: GHSA-2v8p-fqpx-2q3w is a vulnerability in jxl-modular, 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-2v8p-fqpx-2q3w in the wild and no public exploit code.

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

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-2v8p-fqpx-2q3w/ (Markdown: https://insights.sbomify.com/GHSA-2v8p-fqpx-2q3w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2v8p-fqpx-2q3w

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2v8p-fqpx-2q3w/
Summaries are generated and may contain mistakes; the official description above is the record.