https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 19:51:29 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-32814 <p><strong>Affected:</strong> Alpaquita:stream: libheif</p> <p><strong>Affected:</strong> Alpaquita:stream: libheif</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-32814 https://cve.radiocsirt.org/vuln/euvd-2026-319653 EUVD-2026-319653 https://cve.radiocsirt.org/vuln/euvd-2026-319653 https://cve.radiocsirt.org/vuln/fkie_cve-2026-32814 <p>libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, when decoding a HEIF grid image with strict_decoding=false (the default), a corrupted tile silently fails to decode and the library returns heif_error_Ok with no indication of failure, leading to an uninitialized heap memory information leak. The canvas is allocated via create_clone_image_at_new_size() → plane.alloc() → new (std::nothrow) uint8_t[allocation_size] which does not zero the memory; only the alpha plane is explicitly initialized via fill_plane(), so the Y, Cb, and Cr planes contain whatever was previously at that heap address. The failed tile&#39;s region of the canvas is never written. It retains uninitialized heap data that is delivered to the caller as decoded pixel values (4,096 bytes per Y/Cb/Cr plane = 12,288+ bytes total). Any application using libheif to decode grid-based HEIF/AVIF files with default settings is vulnerable: a crafted .heic or .avif file causes 4,096+ bytes of heap memory to appear as pixel values in the decoded image, and the calling application receives heif_error_Ok, so it has no indication the output contains heap garbage. In server-side image processing, an uploaded crafted HEIF decoded and re-encoded (e.g., as PNG/JPEG for thumbnails, CDN, social media) can leak cross-user data such as auth tokens, database results, and other users&#39; image data. This issue has been fixed in version 1.22.0.</p> <p>libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, when decoding a HEIF grid image with strict_decoding=false (the default), a corrupted tile silently fails to decode and the library returns heif_error_Ok with no indication of failure, leading to an uninitialized heap memory information leak. The canvas is allocated via create_clone_image_at_new_size() → plane.alloc() → new (std::nothrow) uint8_t[allocation_size] which does not zero the memory; only the alpha plane is explicitly initialized via fill_plane(), so the Y, Cb, and Cr planes contain whatever was previously at that heap address. The failed tile&#39;s region of the canvas is never written. It retains uninitialized heap data that is delivered to the caller as decoded pixel values (4,096 bytes per Y/Cb/Cr plane = 12,288+ bytes total). Any application using libheif to decode grid-based HEIF/AVIF files with default settings is vulnerable: a crafted .heic or .avif file causes 4,096+ bytes of heap memory to appear as pixel values in the decoded image, and the calling application receives heif_error_Ok, so it has no indication the output contains heap garbage. In server-side image processing, an uploaded crafted HEIF decoded and re-encoded (e.g., as PNG/JPEG for thumbnails, CDN, social media) can leak cross-user data such as auth tokens, database results, and other users&#39; image data. This issue has been fixed in version 1.22.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-32814 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10878-1 <p>gdk-pixbuf-loader-libheif-1.22.2-1.1 on GA media</p> <p>gdk-pixbuf-loader-libheif-1.22.2-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10878-1 https://cve.radiocsirt.org/vuln/suse-su-2026:22153-1 <p>Security update for libheif</p> <p>Security update for libheif</p> https://cve.radiocsirt.org/vuln/suse-su-2026:22153-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-32814 <p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: libheif, Ubuntu:Pro:22.04:LTS: libheif, Ubuntu:24.04:LTS: libheif, Ubuntu:25.10: libheif, Ubuntu:26.04:LTS: libheif</p> <p>libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, when decoding a HEIF grid image with strict_decoding=false (the default), a corrupted tile silently fails to decode and the library returns heif_error_Ok with no indication of failure, leading to an uninitialized heap memory information leak. The canvas is allocated via create_clone_image_at_new_size() → plane.alloc() → new (std::nothrow) uint8_t[allocation_size] which does not zero the memory; only the alpha plane is explicitly initialized via fill_plane(), so the Y, Cb, and Cr planes contain whatever was previously at that heap address. The failed tile&#39;s region of the canvas is never written. It retains uninitialized heap data that is delivered to the caller as decoded pixel values (4,096 bytes per Y/Cb/Cr plane = 12,288+ bytes total). Any application using libheif to decode grid-based HEIF/AVIF files with default settings is vulnerable: a crafted .heic or .avif file causes 4,096+ bytes of heap memory to appear as pixel values in the decoded image, and the calling application receives heif_error_Ok, so it has no indication the output contains heap garbage. In server-side image processing, an uploaded crafted HEIF decoded and re-encoded (e.g., as PNG/JPEG for thumbnails, CDN, social media) can leak cross-user data such as auth tokens, database results, and other users&#39; image data. This issue has been fixed in version 1.22.0.</p> <p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: libheif, Ubuntu:Pro:22.04:LTS: libheif, Ubuntu:24.04:LTS: libheif, Ubuntu:25.10: libheif, Ubuntu:26.04:LTS: libheif</p> <p>libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, when decoding a HEIF grid image with strict_decoding=false (the default), a corrupted tile silently fails to decode and the library returns heif_error_Ok with no indication of failure, leading to an uninitialized heap memory information leak. The canvas is allocated via create_clone_image_at_new_size() → plane.alloc() → new (std::nothrow) uint8_t[allocation_size] which does not zero the memory; only the alpha plane is explicitly initialized via fill_plane(), so the Y, Cb, and Cr planes contain whatever was previously at that heap address. The failed tile&#39;s region of the canvas is never written. It retains uninitialized heap data that is delivered to the caller as decoded pixel values (4,096 bytes per Y/Cb/Cr plane = 12,288+ bytes total). Any application using libheif to decode grid-based HEIF/AVIF files with default settings is vulnerable: a crafted .heic or .avif file causes 4,096+ bytes of heap memory to appear as pixel values in the decoded image, and the calling application receives heif_error_Ok, so it has no indication the output contains heap garbage. In server-side image processing, an uploaded crafted HEIF decoded and re-encoded (e.g., as PNG/JPEG for thumbnails, CDN, social media) can leak cross-user data such as auth tokens, database results, and other users&#39; image data. This issue has been fixed in version 1.22.0.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-32814