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

Published Feb 11, 2026
·
Updated

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

Other sources

Accelerate. An out-of-bounds read was addressed with improved bounds checking.

— Apple

Accounts. A permissions issue was addressed with additional restrictions.

— Apple

APFS. A buffer overflow was addressed with improved bounds checking.

— Apple

App Intents. A logic issue was addressed with improved restrictions.

— Apple

AppleJPEG. This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org.

— Apple

Credit

Seiji Sakurai@@HeapSmasher, Asaf Cohen, Dave G., Vamshi Paili, Tony Gorez for Reverse Society@@tonygo_, CVE-2026-1837, impost0r (ret2plt), David Ige(Beryllium Security), Alan Wang, Christopher W. Fletcher, Hovav Shacham, David Kohlbrenner, Riccardo Paccagnella, Andreas Jaegersberger & Ro Achterberg(Nosebeard Labs), Niels Hofmans(TrendAI Zero Day Initiative), Anonymous(TrendAI Zero Day Initiative), Alex Radocea, Suresh Sundaram, Jiri Ha, Arni Hardarson, Johnny Franks@@zeroxjf, Mihalis Haatainen, Ari Hawking, Ashish Kunwar, Vaagn Vardanian, Nathaniel Oh@@calysteon, popku1337(STAR Labs SG Pte), Billy Jheng Bing Jhong(STAR Labs SG Pte), Pan Zhenpeng@@Peterpan0927(STAR Labs SG Pte), Robert Tran, Aswin kumar Gokulakannan, Ryan Hileman via Xint Code (xint.io), Ruslan Dautov, Anton Pakhunov, Ricardo Prado, Ian van der Wurff (ian.nl), Michael DePlante@@izobashi(TrendAI Zero Day Initiative), Ilya Sc. Jowell A., Peter Malone, Doron Assness, Andy Koo@@andykoo(Hexens), Adriatik Raci, Cantina, Luke Francis, kwak kiyong / kakaogames, Vitaly Simonovich, Adel Bouachraoui, greenbynox, Do Young Park, Yuhao Hu, Yuanming Lai, Chenggang Wu, Zhe Wang, DARKNAVY@@DarkNavyOrg(TrendAI Zero Day Initiative), Daniel Rhea, Luka Rački, wac(TrendAI Zero Day Initiative), Kookhwan Lee(TrendAI Zero Day Initiative), Mateusz Krzywicki (iVerify.io), Maher Azzouzi, Tristan Madani@@TristanInSec(Talence Security), Aisle offensive security research team (Joshua Rogers(Calif), Luigino Camastra(Calif), Igor Morgenstern(Calif), (Calif), Guido Vranken)(Calif), Maher Azzouzi(Calif), Ngan Nguyen(Calif), Khiem Tran, Milad Nasr, Nicholas Carlini with Claude, Anthropic, dr3dd, Kenneth Hsu(Palo Alto Networks), Jérôme DJOUDER, Brendon Tiszka(Google Project Zero), an anonymous researcher, Google Threat Analysis Group, Somair Ansar, Csaba Fitzl@@theevilbit(Iru), Chris Betz(Talence Security), Dhiyanesh Selvaraj@@redroot97, Atul R V, Omar Cerrito, Jorge Welch, Abhay Kailasia@@abhay_kailasia(Safran Mumbai India), Kun Peeks@@SwayZGl1tZyyy, Aswin Kumar Gokula Kannan, wdszzml, Atuin Automated Vulnerability Discovery Engine, beist, Yiğit Can YILMAZ@@yilmazcanyigit, Calif.io in collaboration with Claude, Anthropic Research, Dan Raviv, Peter Malone(Supernetworks), Dave G.(Supernetworks), Alex Radocea(Supernetworks), Pan ZhenPeng@@Peterpan0927(STAR Labs SG Pte), Amy (amys.website), YingQi Shi@@Mas0nShi(DBAppSecurity's WeBin lab), David Ige - Beryllium Security, Gia Bui@@yabeow(Calif), w0wbox, Wang Yu

Affected Software

8 affected componentsFixes available
libjxl
Libjxl Project Libjxl>=0.9.0<=0.11.1
Apple macOS Tahoe<26.5
26.5
Apple iOS<26.5
26.5
Apple iPadOS<26.5
26.5
Apple visionOS<26.5
26.5
Apple tvOS<26.5
26.5
Apple WatchOS<26.5
26.5

Remediation

Patch Available

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

Event History

Feb 11, 2026
CVE Published
via MITRE·03:19 PM
Data Sourced
via MITRE·03:19 PM
DescriptionWeakness
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 11, 2026
Data Sourced
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
DescriptionWeakness
Updated
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
Affected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-1837?

CVE-2026-1837 has been classified as a high-severity vulnerability due to its potential to cause out-of-bounds write issues.

2

How do I fix CVE-2026-1837?

To mitigate CVE-2026-1837, update to the latest version of libjxl where the vulnerability has been addressed.

3

What impact does CVE-2026-1837 have on affected systems?

CVE-2026-1837 can lead to the execution of arbitrary code or data corruption due to uninitialized memory accesses.

4

What versions of libjxl are affected by CVE-2026-1837?

CVE-2026-1837 affects all versions of libjxl prior to the patch that addresses this vulnerability.

5

Is there a workaround for CVE-2026-1837?

Currently, the best approach is to apply the security patch provided for CVE-2026-1837 as no reliable workaround exists.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203