https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 10:05:40 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-352466 EUVD-2026-352466 https://cve.radiocsirt.org/vuln/euvd-2026-352466 https://cve.radiocsirt.org/vuln/fkie_cve-2026-8813 <p>This affects versions of the package exifreader before 4.39.0. A crafted image containing an ICC mluc tag can set an attacker-controlled record count together with a zero record size. During parsing, ExifReader repeatedly processes the same record and appends entries to an array without sufficient bounds validation, causing excessive memory growth. In applications that parse attacker-supplied images, this may lead to denial of service through memory exhaustion.</p> <p>This affects versions of the package exifreader before 4.39.0. A crafted image containing an ICC mluc tag can set an attacker-controlled record count together with a zero record size. During parsing, ExifReader repeatedly processes the same record and appends entries to an array without sufficient bounds validation, causing excessive memory growth. In applications that parse attacker-supplied images, this may lead to denial of service through memory exhaustion.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-8813 https://cve.radiocsirt.org/vuln/ghsa-h64w-w9pr-82m4 <p><strong>Affected:</strong> npm: exifreader</p> <p>### Impact</p> <p>When parsing an image with an embedded ICC profile that contains a crafted `multiLocalizedUnicodeType` (`mluc`) tag, ExifReader can be made to allocate memory proportional to attacker-controlled fields in the tag rather than to the actual size of the input. Processing such an image causes excessive memory consumption and can terminate the host process (out-of-memory).</p> <p>Any application that calls `ExifReader.load()` on untrusted images, for example, user uploads in a web service, is affected. ICC profiles are carried in JPEG, TIFF, PNG, HEIC, AVIF, JPEG XL, and WebP, so the issue is reachable from any of those formats.</p> <p>### Patches</p> <p>Fixed in `exifreader@4.39.0`. Upgrade with:</p> <p>npm install exifreader@latest</p> <p>Bower users consume the bundled `dist/` files from this repository, and the same fix is committed there.</p> <p>### Workarounds</p> <p>If upgrading is not immediately possible, configure a [custom build](https://github.com/mattiasw/ExifReader#configure-a-custom-build) that excludes the `icc` module so that ICC parsing (and therefore this code path) is skipped entirely.</p> <p>### Resources</p> <p>- Patch: https://github.com/mattiasw/ExifReader/commit/c9d88b67e127b2dcc7b46e328df468257fb2dc30</p> <p><strong>Affected:</strong> npm: exifreader</p> <p>### Impact</p> <p>When parsing an image with an embedded ICC profile that contains a crafted `multiLocalizedUnicodeType` (`mluc`) tag, ExifReader can be made to allocate memory proportional to attacker-controlled fields in the tag rather than to the actual size of the input. Processing such an image causes excessive memory consumption and can terminate the host process (out-of-memory).</p> <p>Any application that calls `ExifReader.load()` on untrusted images, for example, user uploads in a web service, is affected. ICC profiles are carried in JPEG, TIFF, PNG, HEIC, AVIF, JPEG XL, and WebP, so the issue is reachable from any of those formats.</p> <p>### Patches</p> <p>Fixed in `exifreader@4.39.0`. Upgrade with:</p> <p>npm install exifreader@latest</p> <p>Bower users consume the bundled `dist/` files from this repository, and the same fix is committed there.</p> <p>### Workarounds</p> <p>If upgrading is not immediately possible, configure a [custom build](https://github.com/mattiasw/ExifReader#configure-a-custom-build) that excludes the `icc` module so that ICC parsing (and therefore this code path) is skipped entirely.</p> <p>### Resources</p> <p>- Patch: https://github.com/mattiasw/ExifReader/commit/c9d88b67e127b2dcc7b46e328df468257fb2dc30</p> https://cve.radiocsirt.org/vuln/ghsa-h64w-w9pr-82m4