<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 08:17:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-356476</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-356476</link>
      <description>EUVD-2026-356476</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-356476</guid>
    </item>
    <item>
      <title>fkie_cve-2026-52834</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-52834</link>
      <description>&lt;p&gt;jxl-oxide is a pure Rust implementation of a JPEG XL decoder. Prior to jxl-grid 0.6.2, decoding a crafted JPEG XL image on a 32-bit platform can overflow length calculations in AlignedGrid::with_alloc_tracker and related grid and subgrid arithmetic. A 65536 x 65536 frame can pass the frame-area limit while overflowing the usize element count, causing modular, VarDCT, or filter rendering paths to allocate a backing buffer smaller than the logical grid. A tiny bitstream-controlled cropped frame combined with a huge canvas or requested region can also reach the vulnerable composition path in crates/jxl-render/src/blend.rs through ordinary render_frame(). Later mutable subgrid and raw-pointer operations can then perform attacker-controlled out-of-bounds writes, causing memory corruption, denial of service, or arbitrary code execution. This issue is fixed in jxl-grid version 0.6.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;jxl-oxide is a pure Rust implementation of a JPEG XL decoder. Prior to jxl-grid 0.6.2, decoding a crafted JPEG XL image on a 32-bit platform can overflow length calculations in AlignedGrid::with_alloc_tracker and related grid and subgrid arithmetic. A 65536 x 65536 frame can pass the frame-area limit while overflowing the usize element count, causing modular, VarDCT, or filter rendering paths to allocate a backing buffer smaller than the logical grid. A tiny bitstream-controlled cropped frame combined with a huge canvas or requested region can also reach the vulnerable composition path in crates/jxl-render/src/blend.rs through ordinary render_frame(). Later mutable subgrid and raw-pointer operations can then perform attacker-controlled out-of-bounds writes, causing memory corruption, denial of service, or arbitrary code execution. This issue is fixed in jxl-grid version 0.6.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-52834</guid>
    </item>
    <item>
      <title>GHSA-5pmv-rx8r-wmv5 — jxl-grid on 32-bit platforms has an out-of-bounds writes due to integer overflow</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5pmv-rx8r-wmv5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: jxl-grid&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;On 32-bit platforms, decoding a crafted image may lead to out-of-bounds writes due to integer overflow in length calculation.&lt;/p&gt;
&lt;p&gt;### Details &amp;amp; PoC&lt;/p&gt;
&lt;p&gt;The test listed below fail under miri with command `cargo +nightly miri test --release -p jxl-grid`&lt;/p&gt;
&lt;p&gt;Or you can use Address Sanitizer, which ignores Rust-specific UB like aliasing but still flags out-of-bounds accesses:&lt;/p&gt;
&lt;p&gt;`RUSTFLAGS=-Zsanitizer=address cargo +nightly test -Zbuild-std -p jxl-grid --release --target x86_64-unknown-linux-gnu`&lt;/p&gt;
&lt;p&gt;The following tests should be appended to `crates/jxl-grid/src/test/subgrids.rs`:&lt;/p&gt;
&lt;p&gt;```rust
mod miri_ub {
    use super::*;&lt;/p&gt;
&lt;p&gt;// `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::&amp;lt;u8&amp;gt;::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);
    }
}
```&lt;/p&gt;
&lt;p&gt;This issue can be reachable through decoding a crafted image in two ways:&lt;/p&gt;
&lt;p&gt;1. **Huge actual frame**
   A frame such as `65536 x 65536` passes the current frame area limit (`2^32 &amp;lt;= 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.&lt;/p&gt;
&lt;p&gt;2. **Huge canvas plus…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: jxl-grid&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;On 32-bit platforms, decoding a crafted image may lead to out-of-bounds writes due to integer overflow in length calculation.&lt;/p&gt;
&lt;p&gt;### Details &amp;amp; PoC&lt;/p&gt;
&lt;p&gt;The test listed below fail under miri with command `cargo +nightly miri test --release -p jxl-grid`&lt;/p&gt;
&lt;p&gt;Or you can use Address Sanitizer, which ignores Rust-specific UB like aliasing but still flags out-of-bounds accesses:&lt;/p&gt;
&lt;p&gt;`RUSTFLAGS=-Zsanitizer=address cargo +nightly test -Zbuild-std -p jxl-grid --release --target x86_64-unknown-linux-gnu`&lt;/p&gt;
&lt;p&gt;The following tests should be appended to `crates/jxl-grid/src/test/subgrids.rs`:&lt;/p&gt;
&lt;p&gt;```rust
mod miri_ub {
    use super::*;&lt;/p&gt;
&lt;p&gt;// `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::&amp;lt;u8&amp;gt;::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);
    }
}
```&lt;/p&gt;
&lt;p&gt;This issue can be reachable through decoding a crafted image in two ways:&lt;/p&gt;
&lt;p&gt;1. **Huge actual frame**
   A frame such as `65536 x 65536` passes the current frame area limit (`2^32 &amp;lt;= 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.&lt;/p&gt;
&lt;p&gt;2. **Huge canvas plus…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5pmv-rx8r-wmv5</guid>
    </item>
    <item>
      <title>RUSTSEC-2026-0151 — Out-of-bounds writes due to integer overflow in jxl-grid on 32-bit platforms</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2026-0151</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: jxl-grid&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Details &amp;amp; PoC&lt;/p&gt;
&lt;p&gt;The test listed below fail under miri with command `cargo +nightly miri test --release -p jxl-grid`&lt;/p&gt;
&lt;p&gt;Or you can use Address Sanitizer, which ignores Rust-specific UB like aliasing but still flags out-of-bounds accesses:&lt;/p&gt;
&lt;p&gt;`RUSTFLAGS=-Zsanitizer=address cargo +nightly test -Zbuild-std -p jxl-grid --release --target x86_64-unknown-linux-gnu`&lt;/p&gt;
&lt;p&gt;The following tests should be appended to `crates/jxl-grid/src/test/subgrids.rs`:&lt;/p&gt;
&lt;p&gt;```rust
mod miri_ub {
    use super::*;&lt;/p&gt;
&lt;p&gt;// `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::&amp;lt;u8&amp;gt;::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);
    }
}
```&lt;/p&gt;
&lt;p&gt;This issue can be reachable through decoding a crafted image in two ways:&lt;/p&gt;
&lt;p&gt;1. **Huge actual frame**
   A frame such as `65536 x 65536` passes the current frame area limit (`2^32 &amp;lt;= 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 su…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: jxl-grid&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Details &amp;amp; PoC&lt;/p&gt;
&lt;p&gt;The test listed below fail under miri with command `cargo +nightly miri test --release -p jxl-grid`&lt;/p&gt;
&lt;p&gt;Or you can use Address Sanitizer, which ignores Rust-specific UB like aliasing but still flags out-of-bounds accesses:&lt;/p&gt;
&lt;p&gt;`RUSTFLAGS=-Zsanitizer=address cargo +nightly test -Zbuild-std -p jxl-grid --release --target x86_64-unknown-linux-gnu`&lt;/p&gt;
&lt;p&gt;The following tests should be appended to `crates/jxl-grid/src/test/subgrids.rs`:&lt;/p&gt;
&lt;p&gt;```rust
mod miri_ub {
    use super::*;&lt;/p&gt;
&lt;p&gt;// `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::&amp;lt;u8&amp;gt;::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);
    }
}
```&lt;/p&gt;
&lt;p&gt;This issue can be reachable through decoding a crafted image in two ways:&lt;/p&gt;
&lt;p&gt;1. **Huge actual frame**
   A frame such as `65536 x 65536` passes the current frame area limit (`2^32 &amp;lt;= 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 su…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2026-0151</guid>
    </item>
  </channel>
</rss>
