CVE-2024-11498: Resource exhaustion via Stack overflow in libjxl
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. Special conditions such as timing or configuration are required.
- Fixed version: libjxl (Alpine:v3.21) 0.10.4-r0; libjxl (Alpine:v3.23) 0.11.1-r0; jpeg-xl (Debian:12) 0.7.0-10+deb12u1.
Low priority for now. Upgrade to libjxl (Alpine:v3.21) 0.10.4-r0; libjxl (Alpine:v3.23) 0.11.1-r0; jpeg-xl (Debian:12) 0.7.0-10+deb12u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 25, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 49th percentile
- CWE
- CWE-400
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Google
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libjxl project | libjxl | cpe:2.3:a:libjxl_project:libjxl |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Google). Independent of NVD's CPE analysis and usually ahead of it.
libjxl libjxl
- 0.11.0 and later · before 65fbec56bc578b6b6ee02a527be70787bbd053b0affected
- 0.10.0-2 and later · before 65fbec56bc578b6b6ee02a527be70787bbd053b0affected
- 0.9.0-3 and later · before 65fbec56bc578b6b6ee02a527be70787bbd053b0affected
- 0.8.0-3 and later · before 65fbec56bc578b6b6ee02a527be70787bbd053b0affected
- 0.7.0-1 and later · before 65fbec56bc578b6b6ee02a527be70787bbd053b0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libjxl project libjxlbefore 0.8.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | libjxl | before 0.10.4-r0 | 0.10.4-r0 |
| Alpine:v3.23 | libjxl | before 0.11.1-r0 | 0.11.1-r0 |
| Debian:12 | jpeg-xl | before 0.7.0-10+deb12u1 | 0.7.0-10+deb12u1 |
| Debian:13 | jpeg-xl | before 0.10.4-2 | 0.10.4-2 |
| openSUSE:Leap 15.5 | libjxl | before 0.8.2-bp155.2.6.1 | 0.8.2-bp155.2.6.1 |
| openSUSE:Leap 15.6 | libjxl | before 0.8.4-bp156.3.3.4 | 0.8.4-bp156.3.3.4 |
| openSUSE:Leap 15.6 | libjxl-gtk | before 0.8.4-bp156.3.3.4 | 0.8.4-bp156.3.3.4 |
| openSUSE:Leap 15.6 | mozjs115 | before 115.4.0-150600.3.6.1 | 115.4.0-150600.3.6.1 |
| openSUSE:Tumbleweed | libjxl | before 0.11.1-1.1 | 0.11.1-1.1 |
| openSUSE:Tumbleweed | mozjs115 | before 115.15.0-4.1 | 115.15.0-4.1 |
| openSUSE:Tumbleweed | mozjs128 | before 128.5.1-3.1 | 128.5.1-3.1 |
| SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | mozjs115 | before 115.4.0-150600.3.6.1 | 115.4.0-150600.3.6.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | libjxl | before 0.10.3-150700.4.9.1 | 0.10.3-150700.4.9.1 |
| SUSE:Package Hub 15 SP5 | libjxl | before 0.8.2-bp155.2.6.1 | 0.8.2-bp155.2.6.1 |
| SUSE:Package Hub 15 SP6 | libjxl | before 0.8.4-bp156.3.3.4 | 0.8.4-bp156.3.3.4 |
| SUSE:Package Hub 15 SP6 | libjxl-gtk | before 0.8.4-bp156.3.3.4 | 0.8.4-bp156.3.3.4 |
Same product
libjxl project: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-27804JPEG XL (aka jpeg-xl) through 0.3.2 allows writable memory corruption.40Plan
- CVE-2023-0645Out of Bounds read in libjxl36Monitor
- CVE-2026-1837libjxl: Out-of-bounds write in grayscale color transformation when using LCMS234Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-35790Jun 16, 2023 · An issue was discovered in dec_patch_dictionary.cc in libjxl before 0.8.2.30Monitor
- ← EarlierCVE-2024-11403Nov 25, 2024 · Out of Bounds Memory Read/Write in libjxl27Monitor
- Later →CVE-2025-12474Feb 11, 2026 · libjxl: Uninitialized memory read in decoder due to incorrect optimization in patch handling9Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:libjxl | 0.10.4-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:jpeg-xl | 0.7.0-10+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:libjxl | 0.11.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:libjxl | 0.8.2-bp155.2.6.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:libjxl-gtk | 0.8.4-bp156.3.3.4 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:mozjs115 | 115.4.0-150600.3.6.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:mozjs128 | 128.5.1-3.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:libjxl | 0.10.3-150700.4.9.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:libjxl | 0.8.2-bp155.2.6.1 · SUSE:Package Hub 15 SP5 | Package registry (OSV) |
| suse:libjxl-gtk | 0.8.4-bp156.3.3.4 · SUSE:Package Hub 15 SP6 | Package registry (OSV) |
| suse:mozjs115 | 115.4.0-150600.3.6.1 · SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.