Vulnerability database
Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.
16 results
Sep 2, 2026libjxl before 0.12 contains an integer underflow vulnerability in the container box parser that allows remote attackers to inject arbitrary metadata by exploitiCVE-2026-82522 · Other software · libjxl · reported by VulnCheckMedium 5.3
libjxl before 0.12 contains an integer underflow vulnerability in the container box parser that allows remote attackers to inject arbitrary metadata by exploiting 64-bit box size truncation to size_t on 32-bit platforms. Attackers can supply a crafted JPEG XL file causing the decoder to parse attacker-controlled codestream bytes as phantom box headers, enabling injection of arbitrary metadata (Exif, XMP, IPTC, JUMBF) and potential out-of-bounds reads.
- Product
- libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 17, 2026Buffer Overflow vulnerability in libjxl v.0.11.2 and before allows a local attacker to obtain sensitive information via the DecodeImageAPNG functionCVE-2026-52584 · Other software · reported by MITREHigh 7.1
Buffer Overflow vulnerability in libjxl v.0.11.2 and before allows a local attacker to obtain sensitive information via the DecodeImageAPNG function
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
May 27, 2026Heap buffer overflow vulnerability in libjxl 0.12.0 via crafted PBM images to the jxl::extras::DecodeImagePNM function in file lib/extras/dec/pnm.cc.CVE-2025-70103 · Other software · reported by MITREHigh 7.3
Heap buffer overflow vulnerability in libjxl 0.12.0 via crafted PBM images to the jxl::extras::DecodeImagePNM function in file lib/extras/dec/pnm.cc.
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Feb 11, 2026A specially-crafted file can cause libjxl's decoder to write pixel data to uninitialized unallocated memory.CVE-2026-1837 · Computers, phones & browsers · Google · reported by cve-coordination@google.comHigh 8.7
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 color space. Buffers allocated for 1-float-per-pixel are used as if they are allocated for 3-float-per-pixel. That happens only if LCMS2 is used as CMS engine. There is another CMS engine available (selected by build flags).
- Product
- libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordgithub.comaccess.redhat.com
Feb 11, 2026A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memory.CVE-2025-12474 · Computers, phones & browsers · Google · reported by cve-coordination@google.comLow 2.3
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.
- Product
- libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Nov 25, 2024There exists a stack buffer overflow in libjxl.CVE-2024-11498 · Other software · libjxl · reported by cve-coordination@google.comMedium 6.9
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 upgrading past commit 65fbec56bc578b6b6ee02a527be70787bbd053b0.
- Product
- libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Nov 25, 2024There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99.CVE-2024-11403 · Other software · libjxl · reported by cve-coordination@google.comMedium 6.9
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 incomplete codes. This could lead to an out-of-bounds write. In jpegli which is released as part of the same project, the same vulnerability is present. However, the relevant buffer is part of a bigger structure, and the code makes no assumptions on the values that could be overwritten. The issue could however cause jpegli to read uninitialised memory, or addresses of functions.
- Product
- libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 16, 2023An issue was discovered in dec_patch_dictionary.cc in libjxl before 0.8.2.CVE-2023-35790 · Other software · Libjxl Project · reported by MITREHigh 7.5
An issue was discovered in dec_patch_dictionary.cc in libjxl before 0.8.2. An integer underflow in patch decoding can lead to a denial of service, such as an infinite loop.
- Product
- Libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Apr 11, 2023An out of bounds read exists in libjxl.CVE-2023-0645 · Other software · Libjxl · reported by cve-coordination@google.comMedium 5.3
An out of bounds read exists in libjxl. An attacker using a specifically crafted file could cause an out of bounds read in the exif handler. We recommend upgrading to version 0.8.1 or past commit https://github.com/libjxl/libjxl/pull/2101/commits/d95b050c1822a5b1ede9e0dc937e43fca1b10159 https://github.com/libjxl/libjxl/pull/2101/commits/d95b050c1822a5b1ede9e0dc937e43fca1b10159
- Product
- Libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 19, 2022libjxl 0.6.1 has an assertion failure in LowMemoryRenderPipeline::Init() in render_pipeline/low_memory_render_pipeline.cc.CVE-2022-34000 · Other software · Libjxl Project · reported by MITREMedium 6.5
libjxl 0.6.1 has an assertion failure in LowMemoryRenderPipeline::Init() in render_pipeline/low_memory_render_pipeline.cc.
- Product
- Libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordgithub.comsecurity.gentoo.org
Dec 31, 2021libjxl b02d6b9, as used in libvips 8.11 through 8.11.2 and other products, has an out-of-bounds write in jxl::ModularFrameDecoder::DecodeGroup (called from jxl:CVE-2021-45928 · Other software · Libjxl Project · reported by MITREMedium 5.5
libjxl b02d6b9, as used in libvips 8.11 through 8.11.2 and other products, has an out-of-bounds write in jxl::ModularFrameDecoder::DecodeGroup (called from jxl::FrameDecoder::ProcessACGroup and jxl::ThreadPool::RunCallState<jxl::FrameDecoder::ProcessSections).
- Product
- Libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordbugs.chromium.orggithub.com
Nov 1, 2021For certain valid JPEG XL images with a size slightly larger than an integer number of groups (256x256 pixels) when processing the groups out of order the decodCVE-2021-22564 · Computers, phones & browsers · Google LLC · reported by cve-coordination@google.comMedium 4.5
For certain valid JPEG XL images with a size slightly larger than an integer number of groups (256x256 pixels) when processing the groups out of order the decoder can perform an out of bounds copy of image pixels from an image buffer in the heap to another. This copy can occur when processing the right or bottom edges of the image, but only when groups are processed in certain order. Groups can be processed out of order in multi-threaded decoding environments with heavy thread load but also with images that contain the groups in an arbitrary order in the file. It is recommended to upgrade past 0.6.0 or patch with https://github.com/libjxl/libjxl/pull/775
- Product
- libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Nov 1, 2021Invalid JPEG XL images using libjxl can cause an out of bounds access on a std::vector<std::vector<T>> when rendering splines.CVE-2021-22563 · Computers, phones & browsers · Google LLC · reported by cve-coordination@google.comMedium 4.5
Invalid JPEG XL images using libjxl can cause an out of bounds access on a std::vector<std::vector<T>> when rendering splines. The OOB read access can either lead to a segfault, or rendering splines based on other process memory. It is recommended to upgrade past 0.6.0 or patch with https://github.com/libjxl/libjxl/pull/757
- Product
- libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 30, 2021libjxl v0.3.7 is affected by a Divide By Zero in issue in lib/extras/codec_apng.cc jxl::DecodeImageAPNG().CVE-2021-36692 · Other software · Libjxl Project · reported by MITREMedium 6.5
libjxl v0.3.7 is affected by a Divide By Zero in issue in lib/extras/codec_apng.cc jxl::DecodeImageAPNG(). When encoding a malicous APNG file using cjxl, an attacker can trigger a denial of service.
- Product
- Libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 30, 2021libjxl v0.5.0 is affected by a Assertion failed issue in lib/jxl/image.cc jxl::PlaneBase::PlaneBase().CVE-2021-36691 · Other software · Libjxl Project · reported by MITREHigh 7.5
libjxl v0.5.0 is affected by a Assertion failed issue in lib/jxl/image.cc jxl::PlaneBase::PlaneBase(). When encoding a malicous GIF file using cjxl, an attacker can trigger a denial of service.
- Product
- Libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 1, 2021JPEG XL (aka jpeg-xl) through 0.3.2 allows writable memory corruption.CVE-2021-27804 · Other software · Libjxl Project · reported by MITRECritical 9.8
JPEG XL (aka jpeg-xl) through 0.3.2 allows writable memory corruption.
- Product
- Libjxl
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordpacketstormsecurity.comseclists.org
Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.