GHSA-66m8-c62j-h6v5Medium· 6.2▾ Sunlitjxl-oxide: `FrameBuffer::new` creates out-of-bounds slices on overflow
▾ Sunlit zone — Low / medium · no exploitation signal
impact 34.1 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
jxl-oxide exposes a public safe API that can construct an undersized FrameBuffer due to unchecked usize multiplication, which immediately trigger panic while initializing the buffer in normal decoding path.
Additionally, calling the safe grouped buffer accessors afterward can create invalid oversized slices from a much smaller allocation, causing undefined behavior; however normal decoding path never reaches UB, because these methods are never used within jxl-oxide.
On 32-bit platforms this can cause panic by accessing out-of-range indices, making it a DoS vulnerability.
jxl-oxide <= 0.12.5Upgrade to a patched release:
jxl-oxide 0.12.6Connected by shared product, vendor, weakness, or advisory.
CVE-2026-52834High· 7.3jxl-oxide is a pure Rust implementation of a JPEG XL decoder
CVE-2026-43618High· 8.1Rsync version 3.4.2 and prior contain an integer overflow vulnerability in the compressed-token decoder where a 32-bit signed counter is not checked for overflow, allowing a malicious sender to trigger an overflow that causes the receive…
CVE-2026-2921High· 7.8GStreamer RIFF Palette Integer Overflow Remote Code Execution Vulnerability
CVE-2026-10649High· 8.6A flaw was found in Pacemaker
CVE-2024-22051Critical· 9.8CommonMarker versions prior to 0.23.4 are at risk of an integer overflow vulnerability
CVE-2026-11774High· 7.6An integer overflow flaw was found in the SASL I/O layer of 389 Directory Server (389-ds-base)