CVE-2024-31989

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

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

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2024-05-21. NVD baseline CVSS 9.0; 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-1545 (ENISA EUVD) · GHSA-9766-5277-j5hr (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
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).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 9.0Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. It has been discovered that an unprivileged pod in a different namespace on the same cluster could connect to the Redis server on port 6379. Despite having installed the latest version of the VPC CNI plugin on the EKS cluster, it requires manual enablement through configuration to enforce network policies. This raises concerns that many clients might unknowingly have open access to their Redis servers. This vulnerability could lead to Privilege Escalation to the level of cluster controller, or to information leakage, affecting anyone who does not have strict access controls on their Redis instance. This issue has been patched in version(s) 2.8.19, 2.9.15 and 2.10.10.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: 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
1.5%
EPSS %ILE
73rd
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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.5% 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

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 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

May 21, 2024

Last Modified

January 9, 2025

Advisory Details (9)

Auto-updated Jul 26, 2026
Patch available. Sources: github_commit, github.
GitHub commit

commit 2de0ceade243 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit 2de0ceade243 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/2de0ceade243039c120c28374016c04ff9590d1d
GitHub advisoryMentions a patch (unverified)

Use of Risky or Missing Cryptographic Algorithms in Redis Cache · Advisory · argoproj/argo-cd · GitHub

https://github.com/argoproj/argo-cd/security/advisories/GHSA-9766-5277-j5hr
GitHub commit

commit f1a449e83ee7 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit f1a449e83ee7 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/f1a449e83ee73f8f14d441563b6a31b504f8d8b0
GitHub commit

commit bdd889d43969 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit bdd889d43969 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/bdd889d43969ba738ddd15e1f674d27964048994
GitHub commit

commit 9552034a8007 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit 9552034a8007 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/9552034a80070a93a161bfa330359585f3b85f07
GitHub commit

commit 6ef7b62a0f67 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit 6ef7b62a0f67 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/6ef7b62a0f67e74b4aac2aee31c98ae49dd95d12
GitHub commit

commit 53570cbd143b (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit 53570cbd143b — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/53570cbd143bced49d4376d6e31bd9c7bd2659ff
GitHub commit

commit 4e2fe302c335 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit 4e2fe302c335 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/4e2fe302c3352a0012ecbe7f03476b0e07f7fc6c
GitHub commit

commit 35a7d6c7fa15 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit 35a7d6c7fa15 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/35a7d6c7fa1534aceba763d6a68697f36c12e678

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-gitops-1/must-gather-rhel8:v1.11.5-32024-05-29redhat
redhatopenshift-gitops-1/must-gather-rhel8:v1.12.3-42024-05-28redhat
redhatopenshift-gitops-1/must-gather-rhel8:v1.10.6-42024-05-28redhat
gogithub.com/argoproj/argo-cd—ghsa
gogithub.com/argoproj/argo-cd/v2 @ 2.8.19 (fixes < 2.8.19)—ghsa
gogithub.com/argoproj/argo-cd/v2 @ 2.9.15 (fixes >= 2.9.0-rc1, < 2.9.15)—ghsa
gogithub.com/argoproj/argo-cd/v2 @ 2.10.10 (fixes >= 2.10.0-rc1, < 2.10.10)—ghsa
gogithub.com/argoproj/argo-cd/v2 @ 2.11.1 (fixes >= 2.11.0-rc1, < 2.11.1)—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

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/argoproj/argo-cd—
  • every version through 1.8.7: no fix on record
  • every version on: no fix on record
—
github.com/argoproj/argo-cd/v2—
  • every version up to 2.8.19: fixed in 2.8.19
  • 2.9.0-rc1 up to 2.9.15: fixed in 2.9.15
  • 2.10.0-rc1 up to 2.10.10: fixed in 2.10.10
  • 2.11.0-rc1 up to 2.11.1: fixed in 2.11.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 76× 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 97 of 255 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 158 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 1.5% · 73rd percentile
  2. 2026-11-02 06:57 UTCEG score recompute
  3. 2026-11-02 06:57 UTCVendor advisory
  4. 2026-11-02 06:56 UTCGHSA enrichmentGHSA-9766-5277-j5hr · GitHub severity CRITICAL · GitHub CVSS 9.0
  5. 2026-11-01 08:14 UTCGHSA enrichmentGHSA-9766-5277-j5hr · GitHub severity CRITICAL · GitHub CVSS 9.0
  6. 2026-11-01 08:14 UTCEG score recompute
  7. 2026-11-01 06:50 UTCEG score recompute
  8. 2026-11-01 06:50 UTCVendor advisory
  9. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-10-31 06:44 UTCEG score recompute
  11. 2026-10-31 06:44 UTCVendor advisory
  12. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  13. 2026-10-30 06:37 UTCEG score recompute
  14. 2026-10-30 06:37 UTCVendor advisory
  15. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  16. 2026-10-29 06:31 UTCEG score recompute
  17. 2026-10-29 06:31 UTCVendor advisory
  18. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  19. 2026-10-28 06:26 UTCEG score recompute
  20. 2026-10-28 06:26 UTCVendor advisory
  21. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  22. 2026-10-27 06:20 UTCEG score recompute
  23. 2026-10-27 06:20 UTCVendor advisory
  24. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  25. 2026-10-26 02:12 UTCVendor advisory
Show 72 more
  1. 2026-10-25 17:12 UTCEG score recompute
  2. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  3. 2026-10-25 02:06 UTCEG score recompute
  4. 2026-10-25 02:06 UTCVendor advisory
  5. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  6. 2026-10-24 01:59 UTCEG score recompute
  7. 2026-10-24 01:59 UTCVendor advisory
  8. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  9. 2026-10-23 01:53 UTCEG score recompute
  10. 2026-10-23 01:53 UTCVendor advisory
  11. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  12. 2026-10-22 01:45 UTCEG score recompute
  13. 2026-10-22 01:45 UTCVendor advisory
  14. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  15. 2026-10-21 01:39 UTCEG score recompute
  16. 2026-10-21 01:39 UTCVendor advisory
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  18. 2026-10-20 01:32 UTCEG score recompute
  19. 2026-10-20 01:32 UTCVendor advisory
  20. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  21. 2026-10-19 00:28 UTCEG score recompute
  22. 2026-10-19 00:28 UTCVendor advisory
  23. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  24. 2026-10-18 07:17 UTCEG score recompute
  25. 2026-10-18 00:20 UTCEG score recompute
  26. 2026-10-18 00:20 UTCVendor advisory
  27. 2026-10-17 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  28. 2026-10-17 00:11 UTCEG score recompute
  29. 2026-10-17 00:11 UTCVendor advisory
  30. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  31. 2026-10-15 21:15 UTCEG score recompute
  32. 2026-10-15 21:15 UTCVendor advisory
  33. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  34. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  35. 2026-10-14 15:17 UTCEG score recompute
  36. 2026-10-14 15:17 UTCVendor advisory
  37. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  38. 2026-10-13 14:39 UTCVendor advisory
  39. 2026-10-12 17:55 UTCEG score recompute
  40. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  41. 2026-10-12 14:23 UTCVendor advisory
  42. 2026-10-11 21:20 UTCEG score recompute
  43. 2026-10-11 16:13 UTCEG score recompute
  44. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  45. 2026-10-10 23:17 UTCOSV refresh
  46. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  47. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  48. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  49. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  50. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  51. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  52. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  53. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  54. 2026-09-30 19:43 UTCEG score recompute
  55. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  56. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  57. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  58. 2026-09-27 13:43 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  59. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  60. 2026-09-26 00:23 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  61. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  62. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  63. 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  64. 2026-09-21 11:19 UTCOSV refresh
  65. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  66. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  67. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  68. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  69. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  70. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  71. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  72. 2026-09-11 09:35 UTCEPSS rescoreEPSS 1.5% · 72nd percentile

Publicly available exploits

(1 reference)

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

  • GitHub PoCvt0x78/CVE-2024-31989
    Published Jul 17, 2024

    Exploit for CVE-2024-31989.

    Open source ↗

Frequently asked(5)

What is CVE-2024-31989?
CVE-2024-31989 is a critical-severity vulnerability; its CVE record was published on May 21, 2024. Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. It has been discovered that an unprivileged pod in a different namespace on the same cluster could connect to the Redis server on port 6379. Despite having installed the latest version of the VPC CNI plugin on the EKS…
When was the CVE record for CVE-2024-31989 published?
The CVE record for CVE-2024-31989 was published on May 21, 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 January 9, 2025; the record at its source may have been updated since.
Is CVE-2024-31989 actively exploited?
CVE-2024-31989 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-31989?
CVE-2024-31989 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2024-31989?
A fix for CVE-2024-31989 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-31989 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-31989

Explore →

Is Your Infrastructure Affected by CVE-2024-31989?

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