argoproj · Argo CD · published 2026-10-13

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

Routine No exploitation evidence; EPSS 0.5%.

CVE-2026-77459 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 43% of all CVEs. This Argo CD vulnerability: CVSS 9.9 (v3.1), a successful attack gives total control of the component. Fixed upstream in Argo CD 3.5.4, 3.4.10, 3.3.15. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Argo CD 3.5.4, 3.4.10, 3.3.15.

Patch events

  1. This monthSecurity release

    OrchestrationArgo CD

    Argo CD security releases: 3.5.4, 3.4.10, 3.3.15

    Upgrade to 3.5.43.4.103.3.15

    Why: CVE-2026-55797: EPSS 2.2% with high severity (CVSS 8.8).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.5% (44th pct)FIRST EPSS v2026.06.15
CVSS base score9.9 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →