Argo Project Argo CD up to 3.6.0-rc1 PostDelete Resource Hooks privileges management

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Argo Project Argo CD up to 2.14.21/3.3.14/3.4.9/3.5.3/3.6.0-rc1. Affected by this issue is some unknown functionality of the component PostDelete Resource Hooks. The manipulation leads to privileges management. This vulnerability is listed as CVE-2026-77459. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Argo Project Argo CD up to 2.14.21/3.3.14/3.4.9/3.5.3/3.6.0-rc1 and classified as problematic. This issue affects an unknown functionality of the component PostDelete Resource Hooks. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-77459 since 08/20/2026. The exploitation is known to be easy. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

Upgrading to version 3.3.15, 3.4.10, 3.5.4 or 3.6.0-rc2 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Project Management Software

Vendor

• Argo Project

Name

• Argo CD

Version

• 2.14.0
• 2.14.1
• 2.14.2
• 2.14.3
• 2.14.4
• 2.14.5
• 2.14.6
• 2.14.7
• 2.14.8
• 2.14.9
• 2.14.10
• 2.14.11
• 2.14.12
• 2.14.13
• 2.14.14
• 2.14.15
• 2.14.16
• 2.14.17
• 2.14.18
• 2.14.19
• 2.14.20
• 2.14.21
• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.3.5
• 3.3.6
• 3.3.7
• 3.3.8
• 3.3.9
• 3.3.10
• 3.3.11
• 3.3.12
• 3.3.13
• 3.3.14
• 3.4.0
• 3.4.1
• 3.4.2
• 3.4.3
• 3.4.4
• 3.4.5
• 3.4.6
• 3.4.7
• 3.4.8
• 3.4.9
• 3.5.0
• 3.5.1
• 3.5.2
• 3.5.3
• 3.6.0-rc1

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion