CVE-2026-52834: Jxl grid Jxl-grid On 32-bit Platforms Has Vulnerability
HIGHCVE-2026-52834 is a HIGH (CVSS 7.3) jxl-grid on 32-bit platforms has vulnerability (CWE-190: Integer Overflow or Wraparound) affecting Jxl grid libraries in the crates.io ecosystem. The issue involves jxl-grid on 32-bit platforms has an out-of-bounds writes due to integer overflow. Remediation is available by upgrading affected packages to version 0.6.2.
CVE-2026-52834 at a Glance
Security Impact
CVSS: 7.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H).
How to Fix CVE-2026-52834
To remediate this vulnerability, upgrade all affected Jxl grid dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade jxl-grid to 0.6.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for jxl-grid
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-52834, inspect your project dependencies for Jxl grid:
inspect dependencies for jxl-grid
Analyze the terminal output to locate any version of Jxl grid in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.6.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-190: Integer Overflow or Wraparound, where the product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. this occurs when an integer value is incremented to a value that is too large to store in the associated representation. when this occurs, the value may become a very small or negative number. In Jxl grid, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-52834 Affected Jxl grid Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
jxl-grid
|
crates.io |
< 0.6.2
|
0.6.2
|
References
Frequently Asked Questions
What is CVE-2026-52834?
Which Jxl grid versions are affected?
What version fixes CVE-2026-52834?
Is jxl-grid affected?
What is the CVSS score of CVE-2026-52834?
What CWE is associated with CVE-2026-52834?
How can I check crates.io dependencies for CVE-2026-52834?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-5pmv-rx8r-wmv5",
"modified" : "2026-07-02T20:45:59Z",
"published" : "2026-07-02T20:45:59Z",
"aliases" : [ "CVE-2026-52834" ],
"summary" : "jxl-grid on 32-bit platforms has an out-of-bounds writes due to integer overflow",
"details" : "### Summary\n\nOn 32-bit platforms, decoding a crafted image may lead to out-of-bounds writes due to integer overflow in length calculation.\n\n### Details & PoC\n\nThe test listed below fail under miri with command `cargo +nightly miri test --release -p jxl-grid`\n\nOr you can use Address Sanitizer, which ignores Rust-specific UB like aliasing but still flags out-of-bounds accesses:\n\n`RUSTFLAGS=-Zsanitizer=address cargo +nightly test -Zbuild-std -p jxl-grid --release --target x86_64-unknown-linux-gnu`\n\nThe following tests should be appended to `crates/jxl-grid/src/test/subgrids.rs`:\n\n```rust\nmod miri_ub {\n use super::*;\n\n // `AlignedGrid::with_alloc_tracker` computes `width * height` unchecked. In release, overflow\n // can create a tiny backing buffer for huge logical dimensions.\n #[test]\n fn aligned_grid_dimension_product_overflows() {\n let width = usize::MAX / 2 + 1;\n let mut grid = AlignedGrid::<u8>::with_alloc_tracker(width, 2, None).unwrap();\n let mut subgrid = grid.as_subgrid_mut();\n *subgrid.get_mut(0, 1) = 1;\n std::hint::black_box(grid);\n }\n}\n```\n\nThis issue can be reachable through decoding a crafted image in two ways:\n\n1. **Huge actual frame**\n 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 `AlignedGrid`s in modular/VarDCT/filter paths and later writes through mutable subgrids.\n\n2. **Huge canvas plus tiny cropped frame**\n This is the more practical “small payload, huge logical output” case. A bitstream-controlled frame crop can be tiny, but if the canvas/default requested region is huge, composition can allocate an output grid sized to the canvas/ROI at crates/jxl-render/src/blend.rs. That is bitstream frame cropping, not API crop. With a 32-bit target and a full requested image region whose area overflows, this can happen through ordinary `render_frame()`.\n\n### Impact\n\nOn 32-bit platforms this can cause out-of-bounds writes with attacker-controlled data when decoding a crafted JPEG XL image. This could allow arbitrary code execution.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "crates.io",
"name" : "jxl-grid"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.6.2"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.6.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/tirr-c/jxl-oxide/security/advisories/GHSA-5pmv-rx8r-wmv5"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/tirr-c/jxl-oxide"
}, {
"type" : "WEB",
"url" : "https://rustsec.org/advisories/RUSTSEC-2026-0151.html"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-122", "CWE-131", "CWE-190" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-02T20:45:59Z",
"nvd_published_at" : null
}
}