How severe is CVE-2026-1837?

CVE-2026-1837 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-1837 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-1837?

CVE-2026-1837 affects Libjxl Project Libjxl. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-1837?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-1837 have an EU (EUVD) identifier?

Yes. CVE-2026-1837 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-6177.

When was CVE-2026-1837 published?

CVE-2026-1837 was published on 2026-02-11 and last updated on 2026-06-30.

CVE-2026-1837

CVE-2026-1837 is a high-severity vulnerability in Libjxl Project Libjxl with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-770.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v4: 8.7
EPSS exploit prediction: 0% (10th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-6177
Weakness: CWE-770
Affected product: Libjxl Project Libjxl
Published: 2026-02-11
Last modified: 2026-06-30

Description

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).

Frequently asked questions

What is CVE-2026-1837?: 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).
How severe is CVE-2026-1837?: CVE-2026-1837 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-1837 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-1837?: CVE-2026-1837 affects Libjxl Project Libjxl. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-1837?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-1837 have an EU (EUVD) identifier?: Yes. CVE-2026-1837 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-6177.
When was CVE-2026-1837 published?: CVE-2026-1837 was published on 2026-02-11 and last updated on 2026-06-30.

References

Affected products (1)

cpe:2.3:a:libjxl_project:libjxl:*:*:*:*:*:*:*:*

More vulnerabilities in Libjxl Project Libjxl

CVE-2024-11403 — Critical (CVSS 9.8): There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99.…
CVE-2021-27804 — Critical (CVSS 9.8): JPEG XL (aka jpeg-xl) through 0.3.2 allows writable memory corruption.
CVE-2024-11498 — High (CVSS 7.5): There exists a stack buffer overflow in libjxl. A specifically-crafted file can cause the JPEG XL decoder to use large…
CVE-2023-35790 — High (CVSS 7.5): An issue was discovered in dec_patch_dictionary.cc in libjxl before 0.8.2. An integer underflow in patch decoding can…
CVE-2021-36691 — High (CVSS 7.5): libjxl v0.5.0 is affected by a Assertion failed issue in lib/jxl/image.cc jxl::PlaneBase::PlaneBase(). When encoding a…
CVE-2022-34000 — Medium (CVSS 6.5): libjxl 0.6.1 has an assertion failure in LowMemoryRenderPipeline::Init() in…

All CVEs affecting Libjxl Project Libjxl →

Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities

CVE-2026-31283 — Critical (CVSS 9.8): In Totara LMS v19.1.5 and before, the forgot password API does not implement rate limiting for the target email…
CVE-2020-37067 — Critical (CVSS 9.8): Filetto 1.0 FTP server contains a denial of service vulnerability in the FEAT command processing that allows attackers…
CVE-2021-47875 — Critical (CVSS 9.8): GeoGebra CAS Calculator 6.0.631.0 contains a denial of service vulnerability that allows attackers to crash the…
CVE-2025-11832 — Critical (CVSS 9.8): Allocation of Resources Without Limits or Throttling vulnerability in Azure Access Technology BLU-IC2, Azure Access…
CVE-2024-44241 — Critical (CVSS 9.8): The issue was addressed with improved bounds checks. This issue is fixed in iOS 18.1 and iPadOS 18.1, macOS Sequoia…
CVE-2022-3439 — Critical (CVSS 9.8): Allocation of Resources Without Limits or Throttling in GitHub repository ikus060/rdiffweb prior to 2.5.0.

Browse all CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities →