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.
CVE-2026-15416
This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.9
- EG Score
- 8.9(medium)
- EPSS
- 20.0%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (6)
Auto-updated Jul 14, 2026Caught 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-codeqlUnpatched Argo CD Repo-Server Flaw Could Let Attackers Take Over Kubernetes Clusters
https://thehackernews.com/2026/07/unpatched-argo-cd-repo-server-flaw.htmlArgo 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-g2g8commit 0f245ab (argoproj/argo-helm)
Patch available: argoproj/argo-helm argo-cd-10.0.0 (contains commit 0f245ab)
https://github.com/argoproj/argo-helm/commit/0f245ab2496732 – (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=2496732Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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.
- 2026-07-15 23:42 UTCEG score recompute
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 10:52 UTCEG score recompute
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 22:03 UTCEG score recompute
- 2026-07-14 09:10 UTCEG score recompute
- 2026-07-14 09:10 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS 91%CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS 97%CRITICAL
- CVE-2018-25134EG 9.8CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2018-21132EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
- CVE-2006-0061EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-15416?
When was CVE-2026-15416 disclosed?
Is CVE-2026-15416 actively exploited?
What is the CVSS score of CVE-2026-15416?
How do I remediate CVE-2026-15416?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15416
Is Your Infrastructure Affected by CVE-2026-15416?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.