CVE-2024-11498: There exists a stack buffer overflow in libjxl. A specifically-crafted file can cause the JPEG XL decoder to u

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

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

Q: Is CVE-2024-11498 being exploited?

CVE-2024-11498 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-11498 affect?

CVE-2024-11498 affects libjxl. Severity is high (CVSS 7.5). There exists a stack buffer overflow in libjxl. A specifically-crafted file can cause the JPEG XL decoder to use large amounts of stack space (up to 256mb is possible, maybe 512mb), potentially exhausting the stack. An attacker can craft a

Q: How urgent is CVE-2024-11498?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

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

There exists a stack buffer overflow in libjxl. A specifically-crafted file can cause the JPEG XL decoder to use large amounts of stack space (up to 256mb is possible, maybe 512mb), potentially exhausting the stack. An attacker can craft a file that will cause excessive memory usage. We recommend upgrading past commit 65fbec56bc578b6b6ee02a527be70787bbd053b0.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-400
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-11498?

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

Is CVE-2024-11498 being exploited?

CVE-2024-11498 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-11498 affect?

CVE-2024-11498 affects libjxl. Severity is high (CVSS 7.5). There exists a stack buffer overflow in libjxl. A specifically-crafted file can cause the JPEG XL decoder to use large amounts of stack space (up to 256mb is possible, maybe 512mb), potentially exhausting the stack. An attacker can craft a

How urgent is CVE-2024-11498?

Priority 43/100. High 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-11403 CRITICAL 9.8 UPGRADE There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33

References

← Back to latest CVEs