CVE-2024-25178

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2025-07-07. NVD baseline CVSS 9.1; sources differ by 0.0.

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

Also known asEUVD-2024-22514 (ENISA EUVD) · GHSA-vw7w-mrf6-7vrv (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

July 7, 2025

Last Modified

November 3, 2025

Advisory Details (5)

Auto-updated Aug 1, 2026
Patch available. Sources: github_commit.
Web page

Stack overflow in error handler during stack overflow · Issue #1152 · LuaJIT/LuaJIT · GitHub

https://github.com/LuaJIT/LuaJIT/issues/1152
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4283-1] luajit security update

https://lists.debian.org/debian-lts-announce/2025/08/msg00022.html
GitHub commit Patch Available

commit defe61a56751 (openresty/luajit2)

Patch available: openresty/luajit2 v2.1-20250826 (contains commit defe61a56751)

https://github.com/openresty/luajit2/commit/defe61a56751a0db5f00ff3ab7b8f45436ba74c8
GitHub commit

commit defe61a56751 (LuaJIT/LuaJIT)

Fix landed in LuaJIT/LuaJIT commit defe61a56751 — awaiting tagged release

https://github.com/LuaJIT/LuaJIT/commit/defe61a56751a0db5f00ff3ab7b8f45436ba74c8

Vendor Advisories for CVE-2024-25178(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuluajit (2.1.0~beta3+dfsg-5.1ubuntu0.18.04.1~esm1) @ bionic2026-11-02ubuntu

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

(10 across 10 ecosystems)
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1_p20240815-r1: fixed in 2.1_p20240815-r1
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1_p20240815-r1: fixed in 2.1_p20240815-r1
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1_p20240815-r1: fixed in 2.1_p20240815-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1_p20240815-r1: fixed in 2.1_p20240815-r1
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1_p20240815-r1: fixed in 2.1_p20240815-r1
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1_p20240815-r1: fixed in 2.1_p20240815-r1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
luajit2.1.0~beta3+dfsg-5.3
  • every version up to 2.1.0~beta3+dfsg-5.3+deb11u1: fixed in 2.1.0~beta3+dfsg-5.3+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
luajit2.1.0~beta3+git20220320+dfsg-4.1
  • every version up to 2.1.0~beta3+git20220320+dfsg-4.1+deb12u1: fixed in 2.1.0~beta3+git20220320+dfsg-4.1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1.0+openresty20240314-1: fixed in 2.1.0+openresty20240314-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1.0+openresty20240314-1: fixed in 2.1.0+openresty20240314-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 27× in last 7d / 93× 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 100 of 262 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. None are among the latest 100 rows. The 162 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-25178?
CVE-2024-25178 is a critical-severity vulnerability; its CVE record was published on July 7, 2025. LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.
When was the CVE record for CVE-2024-25178 published?
The CVE record for CVE-2024-25178 was published on July 7, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2024-25178 actively exploited?
CVE-2024-25178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-25178?
CVE-2024-25178 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2024-25178?
A fix for CVE-2024-25178 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-25178 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-25178?

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