CVE-2026-15416 is a remote code execution vulnerability in Argo CD affecting the repo-server component. The flaw is exposed through the GenerateManifest gRPC endpoint and stems from missing authentication on a critical function, allowing an unauthenticated attacker with network access to the repo-server interface to execute arbitrary code on the repo-server under certain conditions. The issue is particularly significant in GitOps deployments because compromise of the repo-server can be chained with manipulation of Argo CD cached data in Redis, enabling the attacker to cause deployment of malicious Kubernetes resources to clusters managed by Argo CD. In environments where the required network paths are reachable, this creates a path from repo-server compromise to broader control of managed clusters.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An unauthenticated remote code execution vulnerability in Argo CD's repo-server via the generatemanifest gRPC endpoint that can also enable malicious Kubernetes resource deployment and possible full cluster compromise.
An unauthenticated remote code execution vulnerability in the Argo CD repo-server that can, under certain conditions, be chained with Redis cache manipulation to compromise Kubernetes clusters managed by Argo CD.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.