jxl-grid on 32-bit platforms has an out-of-bounds writes due to integer overflow

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H

EPSS

• CVE-2026-52834: 0.17% estimated exploitation activity in the next 30 days; percentile 6.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary On 32-bit platforms, decoding a crafted image may lead to out-of-bounds writes due to integer overflow in length calculation. Details & PoC The test listed below fail under miri with command cargo +nightly miri test --release -p jxl-grid Or you can use Address Sanitizer, which ignores Rust-specific UB like aliasing but still flags out-of-bounds accesses: RUSTFLAGS=-Zsanitizer=address cargo +nightly test -Zbuild-std -p jxl-grid --release --target x8664-unknown-linux-gnu The following tests should be appended to crates/jxl-grid/src/test/subgrids.rs: This issue can be reachable through decoding a crafted image in two ways: 1. Huge actual frame A frame such as 65536 x 65536 passes the current frame area limit (2^32 <= 2^40) but overflows usize element count on 32-bit. Rendering then allocates too-small AlignedGrids in modular/VarDCT/filter paths and later writes through mutable subgrids. 2. Huge canvas plus tiny cropped frame This is the more practical “small payload, huge…

Published by the source

2 Jul 2026, 20:45 UTC

Last modified by the source

2 Jul 2026, 20:46 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5pmv-rx8r-wmv5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-52834

Advisory: jxl-grid on 32-bit platforms has an out-of-bounds writes due to integer overflow
IDs: CVE-2026-52834, GHSA-5pmv-rx8r-wmv5
Record: https://patchnext.com/advisories/cve-2026-52834 (revision 1, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: jxl-grid 0.6.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io jxl-grid: affected <= 0.6.1; fixed in 0.6.2

## Suggested inspection (read-only)
- crates.io jxl-grid: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on jxl-grid.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5pmv-rx8r-wmv5 (GitHub-reviewed advisory GHSA-5pmv-rx8r-wmv5 lists affected ranges: crates.io jxl-grid >=0 <=0.6.1)

Commands are suggestions: review each one before running it.