CVE-2026-1837
libjxl: Out-of-bounds write in grayscale color transformation when using LCMS2
CVSS Score
8.8
EPSS Score
0.0%
EPSS Percentile
0th
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).
| CWE | CWE-805 |
| Vendor | |
| Product | libjxl |
| Ecosystems | |
| Industries | Technology |
| Published | Feb 11, 2026 |
| Last Updated | Jul 15, 2026 |
Stay Ahead of the Next One
Get instant alerts for google libjxl
Be the first to know when new high vulnerabilities affecting google libjxl are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
Affected Versions
Google / libjxl
0.9 ≤ 0.11.1
References
github.com: https://github.com/libjxl/libjxl/issues/4549 access.redhat.com: https://access.redhat.com/security/cve/CVE-2026-1837 bugzilla.redhat.com: https://bugzilla.redhat.com/show_bug.cgi?id=2438974 security.access.redhat.com: https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-1837.json