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.
Published: 2026-10-13
Score: 9.9 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Privilege Escalation and Bypassing Resource Restrictions
Action: Immediate Patch
AI Analysis

Impact

The vulnerability in Argo CD allows an attacker who can modify an Application’s Git repository to add a PostDelete resource hook that bypasses the AppProject destination and resource authorization checks. By committing a delete hook targeted to a forbidden namespace, cluster, group, kind, or resource, the controller creates that resource with cluster credentials when the Application is deleted. This bypass can result in creation or deletion of cluster‑scoped resources, access to disallowed namespaces, and deployment of arbitrary objects, compromising the cluster’s integrity. The weakness is a form of improper authorization (CWE‑863).

Affected Systems

Argo CD versions 2.10.0 through 3.6.0‑rc2 inclusive are affected. The vulnerability is fixed in newer releases that follow these versions, so any deployment using an older release is susceptible.

Risk and Exploitability

The CVSS score of 9.9 indicates a critical severity. The EPSS score is < 1%, indicating a low probability of exploitation but not impossible, and the vulnerability is not listed in CISA KEV. The most likely attack vector requires write access to the Application’s Git repository; once authorized, an attacker can commit a delete hook and trigger the creation of resources with cluster‑wide privileges. The exploitation is straightforward with no additional conditions beyond repository write permission.

Generated by OpenCVE AI on October 20, 2026 at 12:36 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Argo CD to a patched version such as 3.3.15 or later.
  • Review and limit write access to the Git repositories used by Argo CD applications, ensuring only trusted users can commit deletion hooks.
  • If an upgrade cannot be performed immediately, remove or disable the PostDelete hooks in the Application repository and consider temporarily disabling PostDelete hooks in Argo CD.

Generated by OpenCVE AI on October 20, 2026 at 12:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-fmxq-cgp8-87wp Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
History

Tue, 20 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-653
References
Metrics threat_severity

None

threat_severity

Important


Wed, 14 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 13 Oct 2026 19:00:00 +0000

Type Values Removed Values Added
First Time appeared Argoproj
Argoproj argo-cd
Vendors & Products Argoproj
Argoproj argo-cd

Tue, 13 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
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.
Title Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 9.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}


Subscriptions

Argoproj Argo-cd
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-14T15:29:55.346Z

Reserved: 2026-08-20T20:07:49.961Z

Link: CVE-2026-77459

cve-icon Vulnrichment

Updated: 2026-10-14T15:29:45.809Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-13T17:17:46.050

Modified: 2026-10-16T16:00:33.533

Link: CVE-2026-77459

cve-icon Redhat

Severity : Important

Publid Date: 2026-10-07T16:00:00Z

Links: CVE-2026-77459 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-20T12:45:15Z

Weaknesses
  • CWE-653

    Improper Isolation or Compartmentalization

  • CWE-863

    Incorrect Authorization