CVE-2024-11403

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: MODERATE) published 2024-11-25. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-33796 (ENISA EUVD) · GHSA-5pp5-4vfv-784q (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 present. However, the relevant buffer is part of a bigger structure, and the code makes no assumptions on the values that could be overwritten. The issue could however cause jpegli to read uninitialised memory, or addresses of functions.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 25, 2024

Last Modified

July 24, 2025

Advisory Details (1)

Auto-updated Oct 9, 2026
Patch available. Sources: github_commit.
GitHub commit

commit 9cc451b91b74 (libjxl/libjxl)

Fix landed in libjxl/libjxl commit 9cc451b91b74 — awaiting tagged release

https://github.com/libjxl/libjxl/commit/9cc451b91b74ba470fd72bd48c121e9f33d24c99

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibjxl0.7 (0.7.0-10.2ubuntu6.1) @ noble2026-11-01ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jpeg-xl0.7.0-10
  • every version up to 0.7.0-10+deb12u1: fixed in 0.7.0-10+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jpeg-xl—
  • every version up to 0.10.4-2: fixed in 0.10.4-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jpeg-xl—
  • every version up to 0.10.4-2: fixed in 0.10.4-2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 26× in last 7d / 90× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 270 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 172 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-11-01 16:25 UTCEG score recompute
  3. 2026-11-01 16:25 UTCVendor advisory
  4. 2026-11-01 16:25 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub severity MODERATE · GitHub CVSS 9.8
  5. 2026-10-31 18:32 UTCEG score recompute
  6. 2026-10-31 18:32 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  7. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-10-30 20:34 UTCEG score recompute
  9. 2026-10-30 20:34 UTCVendor advisory
  10. 2026-10-30 20:34 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  11. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  12. 2026-10-29 22:42 UTCEG score recompute
  13. 2026-10-29 22:42 UTCVendor advisory
  14. 2026-10-29 22:42 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  15. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  16. 2026-10-29 00:50 UTCEG score recompute
  17. 2026-10-29 00:50 UTCVendor advisory
  18. 2026-10-29 00:50 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  19. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  20. 2026-10-28 02:55 UTCEG score recompute
  21. 2026-10-28 02:54 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  22. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  23. 2026-10-27 04:56 UTCEG score recompute
  24. 2026-10-27 04:56 UTCVendor advisory
  25. 2026-10-27 04:56 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
Show 73 more
  1. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-10-26 02:53 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  3. 2026-10-25 17:23 UTCEG score recompute
  4. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-25 05:00 UTCEG score recompute
  6. 2026-10-25 05:00 UTCVendor advisory
  7. 2026-10-25 05:00 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  8. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-24 07:08 UTCEG score recompute
  10. 2026-10-24 07:08 UTCVendor advisory
  11. 2026-10-24 07:08 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  12. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-23 09:15 UTCEG score recompute
  14. 2026-10-23 09:15 UTCVendor advisory
  15. 2026-10-23 09:15 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  17. 2026-10-22 11:23 UTCEG score recompute
  18. 2026-10-22 11:23 UTCVendor advisory
  19. 2026-10-22 11:23 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  20. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  21. 2026-10-21 13:31 UTCEG score recompute
  22. 2026-10-21 13:31 UTCVendor advisory
  23. 2026-10-21 13:31 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  24. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  25. 2026-10-20 15:32 UTCEG score recompute
  26. 2026-10-20 15:32 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  27. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  28. 2026-10-19 16:15 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  29. 2026-10-18 18:21 UTCEG score recompute
  30. 2026-10-18 18:21 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  31. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  32. 2026-10-18 07:35 UTCEG score recompute
  33. 2026-10-17 20:29 UTCEG score recompute
  34. 2026-10-17 20:29 UTCVendor advisory
  35. 2026-10-17 20:28 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  36. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  37. 2026-10-16 22:35 UTCEG score recompute
  38. 2026-10-16 22:35 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  39. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  40. 2026-10-15 19:15 UTCEG score recompute
  41. 2026-10-15 19:15 UTCVendor advisory
  42. 2026-10-15 19:15 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  43. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  44. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  45. 2026-10-14 13:04 UTCEG score recompute
  46. 2026-10-14 13:04 UTCVendor advisory
  47. 2026-10-14 13:04 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  48. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  49. 2026-10-13 12:59 UTCEG score recompute
  50. 2026-10-13 12:59 UTCVendor advisory
  51. 2026-10-13 12:59 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  52. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  53. 2026-10-12 15:07 UTCEG score recompute
  54. 2026-10-12 15:06 UTCGHSA enrichmentGHSA-5pp5-4vfv-784q · GitHub CVSS 9.8
  55. 2026-10-11 21:33 UTCEG score recompute
  56. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  57. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  58. 2026-10-10 07:25 UTCOSV refresh
  59. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  60. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  61. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  62. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  63. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  64. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  65. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  66. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  67. 2026-09-30 16:42 UTCEG score recompute
  68. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  69. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  70. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  71. 2026-09-27 13:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  72. 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  73. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.6% · 47th percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-11403?
CVE-2024-11403 is a critical-severity vulnerability; its CVE record was published on November 25, 2024. 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…
When was CVE-2024-11403 made public?
CVE-2024-11403 was made public on October 2, 2024: that is the date its CVE record's CNA, Google LLC, gives for when the vulnerability was made public. The CVE record itself was published on November 25, 2024. EchelonGraph's copy of the record carries a last-modified date of July 24, 2025; the record at its source may have been updated since.
Is CVE-2024-11403 actively exploited?
CVE-2024-11403 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-11403?
CVE-2024-11403 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-11403?
A fix for CVE-2024-11403 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-11403

Explore →

Is Your Infrastructure Affected by CVE-2024-11403?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs