High [CVE-2026-15416] Argo CD unauthenticated remote code execution in repo-server via GenerateManifest gRPC endpoint
This high-severity Red Hat Linux advisory covers CVE-2026-15416 affecting Red Hat OpenShift GitOps 1.19.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
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.
Under certain conditions, an unauthenticated attacker with network access to the repo-server gRPC interface could execute arbitrary code and, as part of a multi-stage attack involving the Argo CD Redis cache, potentially compromise Kubernetes clusters managed by Argo CD. Red Hat OpenShift GitOps versions 1.20 and 1.21 are not affected by this vulnerability.
As a result, the unauthenticated gRPC call path required for exploitation is not reachable from other pods in the cluster, and the attack chain cannot be initiated. Red Hat severity: Important — CVSS 8.9 (CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L).
Weakness: CWE-306. Red Hat lists Red Hat Openshift Data Foundation 4; Red Hat OpenShift GitOps as not affected.
Will not fix / out of support: Red Hat OpenShift GitOps. Red Hat fixing advisory: RHSA-2026:52857.
Affected product named by the advisory: Red Hat OpenShift GitOps 1.19.
Is CVE-2026-15416 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-15416 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-15416?
Upgrade to a fixed release named by Red Hat:
- openshift-gitops-1/argocd-rhel8:1785149260
- openshift-gitops-1/gitops-rhel8-operator:1785171339
- RHSA-2026:52857
Confirm against the vendor advisory before you patch.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
- openshift-gitops-1/argocd-rhel8:1785149260
- openshift-gitops-1/gitops-rhel8-operator:1785171339
- RHSA-2026:52857
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
Mitigation checklist
- Limit network access to the Argo CD repo-server gRPC endpoint to trusted internal components using Kubernetes NetworkPolicy or equivalent network access controls. Do not expose the repo-server outside the cluster or to untrusted networks. Restrict access to the associated Redis service and update to a fixed version once one becomes available.
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
Get an email when Red Hat publishes the next one.
See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
- CVE-2026-64849Aug 17, 2026Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.