https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2026-1837.htmlhttps://patchthecve.com/cve/CVE-2026-1837.htmlWed, 15 Jul 2026 02:18:21 +0000HIGH 7.5: A specially-crafted file can cause libjxl's decoder to write pixel data to uninitialized unallocated memory. Soon after that data from another uninitialized unallocated region is copied to pixel data. This can be done by requesting color transformation of grayscale images to another grayscale colorhttps://patchthecve.com/cve/CVE-2025-12474.htmlhttps://patchthecve.com/cve/CVE-2025-12474.htmlWed, 17 Jun 2026 08:32:26 +0000MEDIUM 4.4: A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memory. This can be done by causing the decoder to reference an outside-image-bound area in a subsequent patches. An incorrect optimization causes the decoder to omit populating those areas.https://patchthecve.com/cve/CVE-2024-11498.htmlhttps://patchthecve.com/cve/CVE-2024-11498.htmlWed, 17 Jun 2026 06:57:51 +0000HIGH 7.5: There exists a stack buffer overflow in libjxl. A specifically-crafted file can cause the JPEG XL decoder to use large amounts of stack space (up to 256mb is possible, maybe 512mb), potentially exhausting the stack. An attacker can craft a file that will cause excessive memory usage. We recommend uphttps://patchthecve.com/cve/CVE-2024-11403.htmlhttps://patchthecve.com/cve/CVE-2024-11403.htmlWed, 17 Jun 2026 06:57:41 +0000CRITICAL 9.8: There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99. The JPEG decoder used by the JPEG XL encoder when doing JPEG recompression (i.e. if using JxlEncoderAddJPEGFrame on untrusted input) does not properly check bounds in the presence of