CVE-2026-15416: Argo CD Repo-Server RCE Vulnerability

CVE-2026-15416 Overview

A flaw in Argo CD, the GitOps engine used by Red Hat OpenShift GitOps, allows an unauthenticated attacker with network access to the Argo CD repo-server to achieve remote code execution. Under certain conditions, the attacker can manipulate cached data to deploy malicious Kubernetes resources to managed clusters. Successful exploitation can lead to complete cluster compromise across every environment the repo-server synchronizes.

The issue is tracked under CWE-306: Missing Authentication for Critical Function and was analyzed publicly by Synacktiv using CodeQL.

Critical Impact
Unauthenticated RCE on the Argo CD repo-server enables adversaries to push malicious manifests into managed Kubernetes clusters, resulting in tenant-wide compromise.

Affected Products

Argo CD (upstream GitOps engine)
Red Hat OpenShift GitOps
Argo Helm chart deployments referenced in GHSA-47m3-95c7-g2g8

Discovery Timeline

2026-07-14 - CVE-2026-15416 published to NVD
2026-07-15 - Last updated in NVD database

Technical Details for CVE-2026-15416

Vulnerability Analysis

Argo CD's repo-server component is responsible for fetching Git repositories and rendering Kubernetes manifests through tools such as Helm and Kustomize. The service exposes a gRPC endpoint that, in vulnerable configurations, does not enforce authentication for critical operations. An attacker positioned on the same network segment as the repo-server can invoke these endpoints directly.

Once reachable, the attacker manipulates the rendering pipeline and cached manifests. Because the repo-server output feeds the Argo CD application-controller, poisoned cache entries flow downstream into managed clusters during the next sync cycle. This converts an application-layer flaw into full Kubernetes workload deployment capability.

Root Cause

The root cause is missing authentication on privileged repo-server functionality [CWE-306]. The service trusts callers that reach it over the network, relying on network segmentation instead of cryptographic authentication between Argo CD components. Refer to the Synacktiv analysis for the CodeQL query paths that surface the vulnerable handlers.

Attack Vector

Exploitation requires adjacent network access to the repo-server port, low privileges on the network, and no user interaction. An attacker with a foothold in the cluster network — for example, through a compromised pod, sidecar, or misconfigured NetworkPolicy — can reach the repo-server and inject crafted manifest data. The scope is changed because compromise of the repo-server cascades into every cluster Argo CD manages. See the Red Hat advisory for scope details.

No public proof-of-concept exploit code is available at the time of writing. See The Hacker News coverage for background reporting.

Detection Methods for CVE-2026-15416

Indicators of Compromise

Unexpected gRPC connections to the argocd-repo-server service from pods or IP addresses outside the argocd namespace
New or modified Kubernetes resources deployed by Argo CD that do not correspond to any commit in the source Git repository
Cache entries in the repo-server referencing repositories or revisions that were never registered as Applications
Anomalous child processes spawned by the argocd-repo-server container, such as shells or network utilities

Detection Strategies

Compare rendered manifests applied by Argo CD against the Git source of truth and alert on drift
Monitor Kubernetes audit logs for resource creations by the Argo CD service account that lack a matching Application sync event
Inspect NetworkPolicy coverage for the argocd namespace and alert when traffic reaches the repo-server from unauthorized sources

Monitoring Recommendations

Enable Kubernetes API server audit logging with resource-level granularity and forward events to a centralized analytics platform
Track argocd-repo-server process and syscall telemetry with a runtime workload protection agent
Alert on privileged workloads deployed into namespaces that Argo CD normally does not target

How to Mitigate CVE-2026-15416

Immediate Actions Required

Restrict network access to the argocd-repo-server service using Kubernetes NetworkPolicies so only the argocd-application-controller and argocd-server pods can reach it
Review Argo CD deployments for exposure of the repo-server port outside the cluster and remove any such exposure
Audit recent Argo CD sync history and manifests deployed to managed clusters for unauthorized changes
Rotate credentials and tokens accessible to the repo-server, including Git repository credentials and Helm repository secrets

Patch Information

Refer to the Red Hat security advisory for CVE-2026-15416 and Red Hat Bugzilla #2496732 for the current patch status for Red Hat OpenShift GitOps. The upstream fix is tracked in GHSA-47m3-95c7-g2g8 and the related argo-helm commit 0f245ab. Upgrade to the fixed Argo CD release identified in those advisories.

Workarounds

Enforce a default-deny NetworkPolicy in the argocd namespace and allow only intra-namespace traffic to argocd-repo-server
Deploy the repo-server on dedicated nodes isolated from tenant workloads to reduce adjacent-network exposure
Require mutual TLS between Argo CD components using a service mesh where supported

bash

# Restrict repo-server ingress to Argo CD components only
cat <<EOF | kubectl apply -f -
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: argocd-repo-server-restrict
  namespace: argocd
spec:
  podSelector:
    matchLabels:
      app.kubernetes.io/name: argocd-repo-server
  policyTypes:
    - Ingress
  ingress:
    - from:
        - podSelector:
            matchLabels:
              app.kubernetes.io/part-of: argocd
      ports:
        - protocol: TCP
          port: 8081
EOF