CVE-2024-6678

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2024-09-12. NVD baseline CVSS 9.9; sources differ by 0.0.

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

Also known asEUVD-2024-47729 (ENISA EUVD) · GHSA-ph8h-4mq7-vw5v (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 2.0%CVSS: 9.9Exploit: Public PoCExposed services: Not assessed

Upgrade to versions 17.1.7, 17.2.5, 17.3.2 or above (from the CVE record's solution, GitLab Inc.) — apply it.

An issue was discovered in GitLab CE/EE affecting all versions starting from 8.14 prior to 17.1.7, starting from 17.2 prior to 17.2.5, and starting from 17.3 prior to 17.3.2, which allows an attacker to trigger a pipeline as an arbitrary user under certain circumstances.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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: Upgrade to versions 17.1.7, 17.2.5, 17.3.2 or above (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.
EPSS PROB
2.0%
EPSS %ILE
80th
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

Upgrade to versions 17.1.7, 17.2.5, 17.3.2 or above (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 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 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

September 12, 2024

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Nov 6, 2026
Fix named in the CVE record's solution (GitLab Inc.).
Web page

GitLab Critical Patch Release: 17.3.2, 17.2.5, 17.1.7 | GitLab Docs

https://about.gitlab.com/releases/2024/09/11/patch-release-gitlab-17-3-2-released/

Vendor Advisories for CVE-2024-6678(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 62× 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 283 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 183 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCFaLLenSKiLL1/CVE-2024-6678
    Published May 21, 2026

    PoC for CVE-2024-6678

    Open source ↗

Frequently asked(5)

What is CVE-2024-6678?
CVE-2024-6678 is a critical-severity vulnerability; its CVE record was published on September 12, 2024. An issue was discovered in GitLab CE/EE affecting all versions starting from 8.14 prior to 17.1.7, starting from 17.2 prior to 17.2.5, and starting from 17.3 prior to 17.3.2, which allows an attacker to trigger a pipeline as an arbitrary user under certain circumstances.
When was the CVE record for CVE-2024-6678 published?
The CVE record for CVE-2024-6678 was published on September 12, 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-6678 actively exploited?
CVE-2024-6678 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-6678?
CVE-2024-6678 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2024-6678?
The CVE record's solution for CVE-2024-6678, written by its CNA GitLab Inc., names the fix: "Upgrade to versions 17.1.7, 17.2.5, 17.3.2 or above." The vendor advisories EchelonGraph has for CVE-2024-6678 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-6678?

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