# CVE-2026-77459: Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks

> Attackers with Git write access can bypass Argo CD project restrictions via delete hooks, creating resources in forbidden namespaces or clusters.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** BIT-argo-cd-2026-77459, ECHO-cd0d-ea4a-763c, GHSA-fmxq-cgp8-87wp, GO-2026-6784, MINI-2g2h-8r69-vrwf, MINI-2hwq-x39g-w4qg, MINI-5cwp-q9wc-g6vq, MINI-6654-3wjh-6w57, MINI-66m4-q2jm-cgc3, MINI-6h6m-gx7c-ph9q, MINI-75fp-58fh-26hw, MINI-798r-9rr8-rrfm, MINI-9qp5-663r-vpfc, MINI-c7cw-85vg-mgj3, MINI-cxjq-642f-j427, MINI-cxr8-365j-4w93, MINI-f7ww-vcgf-gf59, MINI-fxfx-72xf-hpg6, MINI-gp8p-p58x-p897, MINI-gq75-x9mx-vj4c, MINI-j5v8-q9jf-hpmq, MINI-jmxw-v97w-h9jg, MINI-m985-mm38-g6jv, MINI-mmx6-qwq3-2528, MINI-q3fj-pgmx-gjfm, MINI-q95x-48jv-48v9, MINI-r23v-m7m7-2m86, MINI-rmrp-9xv7-m6qf

## What is CVE-2026-77459?

CVE-2026-77459 is a critical missing authorization vulnerability in argoproj argo-cd, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 2.10.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, Argo CD creates PostDelete resource hooks without applying the AppProject destination and resource authorization checks used during ordinary synchronization. The omitted checks include cluster-scoped and namespaced resource allow/deny lists. A user who can write to an Application's Git repository can commit a delete hook targeting a forbidden namespace, server, group, kind, or resource name, and deletion of the Application causes the application-controller to create that resource with its destination-cluster credentials. The reachable impact is bounded by the controller's cluster access but can include cluster-scoped resources, disallowed namespaces, persistent hook objects, and secondary objects created by a hook Job. PreSync, Sync, PostSync, and SyncFail hooks continue to use the normal project checks. This issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.

Weakness: CWE-863 (Incorrect Authorization)

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

14 open source packages ship an affected version, including github.com/argoproj/argo-cd/v3, argo-cd and github.com/argoproj/argo-cd.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/argoproj/argo-cd/v3` | Go | From 3.0.0 | 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2 |
| `github.com/argoproj/argo-cd/v3` | Go | From 3.0.0 | 3.3.15 |
| `github.com/argoproj/argo-cd/v3` | Go | From 3.0.0 | 3.3.15 |
| `github.com/argoproj/argo-cd/v3` | Go | From 3.4.0 | 3.4.10 |
| `github.com/argoproj/argo-cd/v3` | Go | From 3.4.0 | 3.4.10 |
| `github.com/argoproj/argo-cd/v3` | Go | From 3.5.0 | 3.5.4 |
| `github.com/argoproj/argo-cd/v3` | Go | From 3.5.0 | 3.5.4 |
| `github.com/argoproj/argo-cd/v3` | Go | From 3.6.0-rc1 | 3.6.0-rc2 |
| `github.com/argoproj/argo-cd/v3` | Go | From 3.6.0-rc1 | 3.6.0-rc2 |
| `argo-cd` | Bitnami | From 2.10.0 | 3.3.15, 3.4.10, 3.5.4 |
| `github.com/argoproj/argo-cd` | Go | All versions | None |
| `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0 | None |
| `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0 to 2.14.21 | None |
| `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0 to 2.14.21 | None |

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

Upgrade github.com/argoproj/argo-cd/v3 to a fixed version for your release line: 3.3.15, 3.4.10, 3.5.4 or 3.6.0-rc2.

## Is CVE-2026-77459 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77459 is a critical missing authorization vulnerability in argoproj argo-cd, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77459 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/argoproj/argo-cd/v3 (Go): affected from 3.0.0; fixed in 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2
- github.com/argoproj/argo-cd/v3 (Go): affected from 3.0.0; fixed in 3.3.15
- github.com/argoproj/argo-cd/v3 (Go): affected from 3.0.0; fixed in 3.3.15
- github.com/argoproj/argo-cd/v3 (Go): affected from 3.4.0; fixed in 3.4.10
- github.com/argoproj/argo-cd/v3 (Go): affected from 3.4.0; fixed in 3.4.10
- github.com/argoproj/argo-cd/v3 (Go): affected from 3.5.0; fixed in 3.5.4
- github.com/argoproj/argo-cd/v3 (Go): affected from 3.5.0; fixed in 3.5.4
- github.com/argoproj/argo-cd/v3 (Go): affected from 3.6.0-rc1; fixed in 3.6.0-rc2
- github.com/argoproj/argo-cd/v3 (Go): affected from 3.6.0-rc1; fixed in 3.6.0-rc2
- argo-cd (Bitnami): affected from 2.10.0; fixed in 3.3.15, 3.4.10, 3.5.4
- github.com/argoproj/argo-cd (Go): affected all versions; no fix listed
- github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0; no fix listed

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-77459/ (Markdown: https://insights.sbomify.com/CVE-2026-77459/index.md)
```

## Sources

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

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