CVE-2024-5128

CRITICALNVD 8.89.4
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.4 from GitHub Security Advisory (severity: CRITICAL) published 2024-06-06. NVD baseline CVSS 8.8; sources differ by 0.6.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2024-46385 (ENISA EUVD) · GHSA-7g45-4xm2-qxvf (GitHub Security Advisories)Source: ENISA EUVD

9.4EG
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.5%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

An Insecure Direct Object Reference (IDOR) vulnerability was identified in lunary-ai/lunary, affecting versions up to and including 1.2.2. This vulnerability allows unauthorized users to view, update, or delete any dataset_prompt or dataset_prompt_variation within any dataset or project. The issue stems from improper access control checks in the dataset management endpoints, where direct references to object IDs are not adequately secured against unauthorized access. This vulnerability was fixed in version 1.2.25.

CVSS v3
8.8
EG Score
9.4CRITICALmedium confidence
EG Risk
73
EG Risk 73/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)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
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.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 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, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. 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 total (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)3 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 total (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

June 6, 2024

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Aug 30, 2026
Fix named in the CVE record.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/11248071-11b2-42d9-991a-504bf2044332

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 59× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 277 rows 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 177 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-5128?
CVE-2024-5128 is a critical-severity vulnerability; its CVE record was published on June 6, 2024. An Insecure Direct Object Reference (IDOR) vulnerability was identified in lunary-ai/lunary, affecting versions up to and including 1.2.2. This vulnerability allows unauthorized users to view, update, or delete any dataset_prompt or dataset_prompt_variation within any dataset or project. The issue…
When was the CVE record for CVE-2024-5128 published?
The CVE record for CVE-2024-5128 was published on June 6, 2024. 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 21, 2024; the record at its source may have been updated since.
Is CVE-2024-5128 actively exploited?
CVE-2024-5128 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-5128?
CVE-2024-5128 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.4 (CRITICAL).
How do I remediate CVE-2024-5128?
The CVE record for CVE-2024-5128 names the fix: "This vulnerability was fixed in version 1.2.25."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-5128

Explore →

Is Your Infrastructure Affected by CVE-2024-5128?

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

Book a Demo →Browse All CVEs