# CVE-2026-15416: Argo-cd: argo cd unauthenticated remote code execution in repo-server via generatemanifest grpc endpoint

> Unauthenticated attackers can execute code on the repo-server and compromise managed Kubernetes clusters via the GenerateManifest gRPC endpoint.

- **Severity:** High 8.9 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 11 Aug 2026

## What is CVE-2026-15416?

CVE-2026-15416 is a high-severity authentication bypass vulnerability in Red Hat OpenShift GitOps, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-15416?


## How do I fix CVE-2026-15416?

No fix has been published for CVE-2026-15416 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15416 being exploited?

There is no known exploitation of CVE-2026-15416 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15416 and fix it if it is affected.

What it is: CVE-2026-15416 is a high-severity authentication bypass vulnerability in Red Hat OpenShift GitOps, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15416 in the wild and no public exploit code.

Affected product: Red Hat OpenShift GitOps. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15416/ (Markdown: https://insights.sbomify.com/CVE-2026-15416/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15416
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15416
- OSV: https://osv.dev/vulnerability/CVE-2026-15416

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15416/
Summaries are generated and may contain mistakes; the official description above is the record.