CVE-2024-11403: There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33

Q: How do I fix CVE-2024-11403?

libjxl: upgrade to 0.8.4. Exact commands for each OS are on this page.

Q: Is CVE-2024-11403 being exploited?

CVE-2024-11403 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-11403 affect?

CVE-2024-11403 affects libjxl. Severity is critical (CVSS 9.8). There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99. The JPEG decoder used by the JPEG XL encoder when doing JPEG recompression (i.e. if using JxlEncoderAddJPEGFrame on untrus

Q: How urgent is CVE-2024-11403?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2024-11403 is a critical-severity flaw (CVSS 9.8) affecting libjxl. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99. The JPEG decoder used by the JPEG XL encoder when doing JPEG recompression (i.e. if using JxlEncoderAddJPEGFrame on untrusted input) does not properly check bounds in the presence of incomplete codes. This could lead to an out-of-bounds write. In jpegli which is released as part of the same project, the same vulnerability is prese

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-125, CWE-787
Published	2024-11-25
Last modified	2026-06-17

Publisher (CNA): Google Inc. · Vendor: libjxl project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-11-25 14:15 UTCPublished CVE record published
2026-06-17 06:57 UTCUpdated Record last modified

libjxl project libjxl UPGRADE

Affected: < 0.8.4

Fixed in: 0.8.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libjxl || rpm -q libjxl || libjxl --version

2. UPGRADE to 0.8.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libjxl

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libjxl

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-11403?

libjxl: upgrade to 0.8.4. Exact commands for each OS are on this page.

Is CVE-2024-11403 being exploited?

CVE-2024-11403 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-11403 affect?

CVE-2024-11403 affects libjxl. Severity is critical (CVSS 9.8). There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99. The JPEG decoder used by the JPEG XL encoder when doing JPEG recompression (i.e. if using JxlEncoderAddJPEGFrame on untrus

How urgent is CVE-2024-11403?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-1837 HIGH 7.5 UPGRADE A specially-crafted file can cause libjxl's decoder to write pixel data to uninitialized unallocated memory
CVE-2025-12474 MEDIUM 4.4 UPGRADE A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memo
CVE-2024-11498 HIGH 7.5 UPGRADE There exists a stack buffer overflow in libjxl. A specifically-crafted file can cause the JPEG XL decoder to u

References

← Back to latest CVEs