CVE-2026-15416

HIGHPre-NVD 8.98.9—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% 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, secondary
Trending — 3 sources updated this week
8.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.9Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was identified in Argo CD, the GitOps engine used by Red Hat OpenShift GitOps, that could allow an unauthenticated attacker with network access to the Argo CD repo-server to achieve remote code execution. Under certain conditions, the attacker may then manipulate cached data to deploy malicious Kubernetes resources to managed clusters, potentially resulting in complete cluster compromise.

CVSS v3
8.9
EG Score
8.9(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity89% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 11, 2026

Advisory Details (6)

Auto-updated Jul 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github, redhat.
generic🟡 PoC Available

Caught in the Octopus Trap: Unauthenticated RCE in Argo CD with CodeQL

https://www.synacktiv.com/en/publications/caught-in-the-octopus-trap-unauthenticated-rce-in-argo-cd-with-codeql
generic

Unpatched Argo CD Repo-Server Flaw Could Let Attackers Take Over Kubernetes Clusters

https://thehackernews.com/2026/07/unpatched-argo-cd-repo-server-flaw.html
github Patch Available

Argo CD: Network policies securing repo-server are not installed by default leading to RCE · Advisory · argoproj/argo-helm · GitHub

https://github.com/argoproj/argo-helm/security/advisories/GHSA-47m3-95c7-g2g8
github_commit Patch Available

commit 0f245ab (argoproj/argo-helm)

Patch available: argoproj/argo-helm argo-cd-10.0.0 (contains commit 0f245ab)

https://github.com/argoproj/argo-helm/commit/0f245ab
redhat

2496732 – (CVE-2026-15416) CVE-2026-15416 argo-cd: Argo CD unauthenticated remote code execution in repo-server via GenerateManifest gRPC endpoint

https://bugzilla.redhat.com/show_bug.cgi?id=2496732
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-15416

Vendor Advisories for CVE-2026-15416(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 / EcosystemFixed in / PatchReleasedSource
redhatopenshift-gitops-1/gitops-rhel8-operator:17851713392026-08-10redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 86× 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 113 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-15416?
CVE-2026-15416 is a high vulnerability published on July 14, 2026. A flaw was identified in Argo CD, the GitOps engine used by Red Hat OpenShift GitOps, that could allow an unauthenticated attacker with network access to the Argo CD repo-server to achieve remote code execution. Under certain conditions, the attacker may then manipulate cached data to deploy…
When was CVE-2026-15416 disclosed?
CVE-2026-15416 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15416 actively exploited?
CVE-2026-15416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.2% of all scored CVEs.
What is the CVSS score of CVE-2026-15416?
CVE-2026-15416 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2026-15416?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15416, 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

Explore the affected products and dependency analysis for CVE-2026-15416

Explore →

Is Your Infrastructure Affected by CVE-2026-15416?

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

Start Free Scan →Browse All CVEs