Memory corruption via LCMS2 grayscale channel mismatch
Published Feb 11, 2026 · Updated Feb 11, 2026
Out-of-bounds write in Google libjxl 0.9 through 0.11.1 allows attackers to corrupt memory by decoding a crafted JPEG XL file. The LCMS2-backed CmsStage::ProcessRow path allocates one float per grayscale pixel but processes the buffer as three floats per pixel. Reachability requires an application to select LCMS2 and request a grayscale-to-grayscale transform, enabling a crash or code execution in that application's context.
Summary
What happened
Out-of-bounds write in Google libjxl 0.9 through 0.11.1 allows attackers to corrupt memory by decoding a crafted JPEG XL file. The LCMS2-backed CmsStage::ProcessRow path allocates one float per grayscale pixel but processes the buffer as three floats per pixel. Reachability requires an application to select LCMS2 and request a grayscale-to-grayscale transform, enabling a crash or code execution in that application's context.
The record
- CVE
- CVE-2026-1837
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- Go standard library
- Product
- libjxl
- Classifications
- CWE-805, CWE-770, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2026CVE publishedPublication date reported by the CVE source.
- Feb 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.9 <=0.11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- grayscale_linear.jxl crash reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo