CVE-2024-31989

CRITICALNVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 1.5%, top 29% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.0Exploit: Elevated riskExposed: 0

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.0(medium)
EG Risk
57(Track*)
EG Risk 57/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
71%
KEV
Not listed

Published

May 21, 2024

Last Modified

January 9, 2025

Advisory Details (9)

Auto-updated Jul 26, 2026
🔬 Proof of concept available. 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 Patch Available🟡 PoC Available

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

Vendor Advisories for CVE-2024-31989(3)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-gitops-1/must-gather-rhel8:v1.11.5-32024-05-29redhat
redhatopenshift-gitops-1/must-gather-rhel8:v1.10.6-42024-05-28redhat
redhatopenshift-gitops-1/must-gather-rhel8:v1.12.3-42024-05-28redhat

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 rangeFixed inDependents
github.com/argoproj/argo-cd———
github.com/argoproj/argo-cd/v2—2.11.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 108 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCvt0x78/CVE-2024-31989
    First seen Jul 17, 2024

    Exploit for CVE-2024-31989.

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-31989?
CVE-2024-31989 is a critical vulnerability 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 CVE-2024-31989 disclosed?
CVE-2024-31989 was first published in the National Vulnerability Database on May 21, 2024, with the most recent update on January 9, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-31989 actively exploited?
CVE-2024-31989 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 28.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-31989, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs