Skip to content

← Public intelligence

crates.io package

jxl-grid

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.3crates.ioPublished

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

    CVE-2026-52834 · GHSA-5pmv-rx8r-wmv5

    Affected
    • crates.io jxl-grid <= 0.6.1
    Fixed in
    0.6.2· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 0.6.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →