ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-77459

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.

Published Oct 13, 2026 · catalog updated Oct 15, 2026 · Argo CD is a

Check if you run it

No confirmed exploitation is on record for CVE-2026-77459. EPSS is 0.72%. Act only if a listed version of Argo CD is a is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Argo CD is a).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.72%
Remediation
Version ranges on file
Affected products
go github.com/argoproj/argo-cd/v2 · go github.com/argoproj/argo-cd/v3 · golang github.com

### Impact Argo CD checks an Application's AppProject before it creates resources during a sync. That check covers destination namespaces and servers, cluster-scoped resource allow and deny lists, and namespaced resource allow and deny lists, including resource names. PreDelete and PostDelete hooks skip it. When the Application is deleted, Argo CD creates those hooks with the application-controller's credentials on the destination cluster. All versions from v2.10.0 onward are affected, including every currently supported release. v2.9.22 and earlier are not. PostDelete hooks were introduced in [dcc17f70bf](https://github.com/argoproj/argo-cd/commit/dcc17f70bf7db973fe480b8b613189b2c5ac4b4b) (2023-12-18, [#16595](https://github.com/argoproj/argo-cd/pull/16595)) and first released in v2.10.0. That creation path has never applied the project check. PreDelete hooks, added in [3bf3d8a212](https://github.com/argoproj/argo-cd/commit/3bf3d8a2124e772ac651f3fd42375c4e9b8008af) (2025-12-05, [#22288](https://github.com/argoproj/argo-cd/pull/22288)) and first released in v3.3.0, use the same path. v3.2.12 and earlier do not have PreDelete hooks. PreSync, Sync, PostSync, and SyncFail hooks still go through the project check. A user who can push to the Git repository an Application syncs from can commit a hook whose namespace, group, kind, or name the AppProject would refuse on sync. The controller adds the delete finalizer when it sees the hook, and the Application stays Synced until someone deletes it. Deleting the Application creates the hook. What that can reach is bounded by the application-controller's access to the destination cluster. In a typical install that access is broad, so a tenant can create a cluster-scoped object such as a , or an object in a namespace the project does not allow. A hook with no deletion policy is removed after it succeeds. A deletion policy that does not remove the hook on success leaves the object in the cluster. A hook such as a Job can create f

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • go github.com/argoproj/argo-cd/v2>= 2.10.0, <= 2.14.21
  • go github.com/argoproj/argo-cd/v2>=2.10.0 <=2.14.21
  • go github.com/argoproj/argo-cd/v3>= 3.0.0, < 3.3.15
  • go github.com/argoproj/argo-cd/v3>= 3.4.0, < 3.4.10
  • go github.com/argoproj/argo-cd/v3>= 3.5.0, < 3.5.4
  • go github.com/argoproj/argo-cd/v3>= 3.6.0-rc1, < 3.6.0-rc2
  • go github.com/argoproj/argo-cd/v3>=3.0.0 <3.3.15||>=3.4.0 <3.4.10||>=3.5.0 <3.5.4||>=3.6.0-rc1 <3.6.0-rc2
  • golang github.comversion unspecified

How to fix CVE-2026-77459

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-77459. EPSS is 0.72%. Act only if a listed version of Argo CD is a is installed.

Which versions are affected?

Compare what you have installed with >= 2.10.0, <= 2.14.21, >=2.10.0 <=2.14.21, >= 3.0.0, < 3.3.15, >= 3.4.0, < 3.4.10, >= 3.5.0, < 3.5.4, >= 3.6.0-rc1, < 3.6.0-rc2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-863: Incorrect Authorization. EPSS 0.72%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Kubernetes security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 13, 2026 · NIST NVD

    Detected

    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 A

  2. Oct 14, 2026 · NIST NVD

    Updated

    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 A

  3. Oct 15, 2026 · GitHub Advisory Database

    Updated

    ### Impact Argo CD checks an Application's AppProject before it creates resources during a sync. That check covers destination namespaces and servers, cluster-scoped resource allow and deny lists, and namespaced resource allow and deny lists, including resource names. PreDelete and PostDelete hooks skip it. When the Application is deleted, Argo CD creates those hooks with the application-controlle

Sources

  • CVE.orgVulnerability recordCVE-2026-77459

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-77459

    30-day exploitation probability 0.7%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-fmxq-cgp8-87wp

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

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-77459

    Argo CD checks an Application's AppProject before it creates resources during a sync. That check covers destination namespaces and servers, cluster-scoped resource allow and deny lists, and namespaced resource allow and deny lists, including resource names. PreDelete and PostDelete hooks skip it. When the Application is deleted, Argo CD creates those hooks with the application-controller's credent

    advisories.gitlab.com
  • GitLab Advisory DatabasePackage advisorygo/github.com/argoproj/argo-cd/v2/CVE-2026-77459.yml

    Argo CD checks an Application's AppProject before it creates resources + during a sync. That check covers destination namespaces and servers, cluster-scoped + resource allow and deny lists, and namespaced resource allow and deny lists, including + resource names. PreDelete and PostDelete hooks skip it. When the Application is + deleted, Argo CD creates those hooks with the application-controller's

    gitlab.com
  • GitLab Advisory DatabasePackage advisorygo/github.com/argoproj/argo-cd/v3/CVE-2026-77459.yml

    Argo CD checks an Application's AppProject before it creates resources + during a sync. That check covers destination namespaces and servers, cluster-scoped + resource allow and deny lists, and namespaced resource allow and deny lists, including + resource names. PreDelete and PostDelete hooks skip it. When the Application is + deleted, Argo CD creates those hooks with the application-controller's

    gitlab.com
  • NIST NVDVulnerability recordCVE-2026-77459

    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 synchroni

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.