Vulnerability in jxl-grid (CVE-2026-52834)
Summary
Vulnerability in jxl-grid (CVE-2026-52834). Risk of unauthorized operations or information disclosure. Exploitable via usize. Mitigation: upgrade to 0.6.2 or later.
Original description
The description as published by the source.
On 32-bit platforms, decoding a crafted image may lead to out-of-bounds writes due to integer overflow in length calculation. This could allow arbitrary code execution.
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 x86_64-unknown-linux-gnu
The following tests should be appended to crates/jxl-grid/src/test/subgrids.rs:
mod miri_ub {
use super::*;
// `AlignedGrid::with_alloc_tracker` computes `width * height` unchecked. In release, overflow
// can create a tiny backing buffer for huge logical dimensions.
#[test]
fn aligned_grid_dimension_product_overflows() {
let width = usize::MAX / 2 + 1;
let mut grid = AlignedGrid::::with_alloc_tracker(width, 2, None).unwrap();
let mut subgrid = grid.as_subgrid_mut();
*subgrid.get_mut(0, 1) = 1;
std::hint::black_box(grid);
}
}
This issue can be reachable through decoding a crafted image in two ways:
- Huge actual frame
A frame such as65536 x 65536passes the current frame area limit (2^32 <= 2^40) but overflowsusizeelement count on 32-bit. Rendering then allocates too-smallAlignedGrids in modular/VarDCT/filter paths and later writes through mutable subgrid…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-52834 has been found in jxl-grid.
Attackers can target a specific entry point like usize over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.3/10.
What to do: upgrade jxl-grid to 0.6.2 or later.
If unsure, ask your IT team or search "jxl-grid CVE-2026-52834" on the vendor's site.
CVE-2026-52834 (jxl-grid) — CWE-122 / CVSS v3 7.3
Attack vector: local / unauthenticated / no user interaction
Attack surface: usize / AlignedGrid
Patched: 0.6.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-122) exists in jxl-grid. Attackers reach the vulnerable code path via usize without authentication.
Check the vendor advisory for the affected versions of jxl-grid. Attack surface: usize / AlignedGrid.
Severity: High (CVSS 7.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.6.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jxl-grid' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jxl-grid' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
jxl-gridを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade jxl-grid to 0.6.2ステージング環境で 0.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory rustsec.org
- package crates.io
- package github.com
- web security-advisories@github.com
- web github.com
- web github.com
- web security-advisories@github.com