CVE-2024-52009

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-3255 (ENISA EUVD) · GHSA-gppm-hq3p-h4rp (GitHub Security Advisories) · GO-2024-3265 (OSV.dev)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.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. Atlantis logs contains GitHub credentials (tokens ghs_...) when they are rotated. This enables an attacker able to read these logs to impersonate Atlantis application and to perform actions on GitHub. When Atlantis is used to administer a GitHub organization, this enables getting administration privileges on the organization. This was reported in #4060 and fixed in #4667 . The fix was included in Atlantis v0.30.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.

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.7% × 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.7%
EPSS %ILE
54th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% 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 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 8, 2024

Last Modified

September 29, 2025

Advisory Details (5)

Auto-updated Oct 9, 2026
Patch available. Sources: github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Git credentials are exposed in atlantis logs · Advisory · runatlantis/atlantis · GitHub

https://github.com/runatlantis/atlantis/security/advisories/GHSA-gppm-hq3p-h4rp
GitHub release Patch Available

v0.30.0

Patch available: runatlantis/atlantis v0.30.0

https://github.com/runatlantis/atlantis/releases/tag/v0.30.0
GitHub pull request

fix: dont log GitHub app token in logs

Fix merged in runatlantis/atlantis PR #4667 on 2024-09-06 — awaiting tagged release

https://github.com/runatlantis/atlantis/pull/4667
Web page

Git credentials are exposed in atlantis logs · Issue #4060 · runatlantis/atlantis · GitHub

https://github.com/runatlantis/atlantis/issues/4060
Web page

Overview - Argo CD - Declarative GitOps CD for Kubernetes

https://argo-cd.readthedocs.io/en/stable/operator-manual/security

Vendor Advisories for CVE-2024-52009(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
gogithub.com/runatlantis/atlantis @ 0.30.0 (fixes < 0.30.0)—ghsa

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/runatlantis/atlantis—
  • every version up to 0.30.0: fixed in 0.30.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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 270 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 170 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-52009?
CVE-2024-52009 is a critical-severity vulnerability; its CVE record was published on November 8, 2024. Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. Atlantis logs contains GitHub credentials (tokens ghs_...) when they are rotated. This enables an attacker able to read these logs to impersonate Atlantis application and to perform actions on…
When was the CVE record for CVE-2024-52009 published?
The CVE record for CVE-2024-52009 was published on November 8, 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 September 29, 2025; the record at its source may have been updated since.
Is CVE-2024-52009 actively exploited?
CVE-2024-52009 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-52009?
CVE-2024-52009 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-52009?
A fix for CVE-2024-52009 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-52009 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-52009

Explore →

Is Your Infrastructure Affected by CVE-2024-52009?

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