Buffer overflow in Google Libjxl

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

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

EPSS exploit prediction

EPSS: 0.003 (19.0th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 19th percentile — 19.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-1837: held from 0.003 to 0.003.

EPSS over last 30 days · oldest: 0.003 · newest: 0.003 · change: +0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-1837?
CVE-2026-1837 is a high-severity vulnerability in Google Libjxl, classified under Buffer Access with Incorrect Length Value. CVSS score: 7.5/10. Published 2026-02-11.
How severe is CVE-2026-1837?
High severity. CVSS v3 base score is 7.5 out of 10.