Skip to content
Fencer Vulns
critical 9.9

CVE-2026-77459 json

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

published 2026-10-13 26 d ago modified 2026-10-20 19 d ago also BIT-argo-cd-2026-77459 , EUVD-2026-98917 , GHSA-fmxq-cgp8-87wp , GO-2026-6784

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/argoproj/argo-cd/v3 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2
  • bitnami argo-cd 3.3.15, 3.4.10, 3.5.4
  • linuxfoundation argo-cd 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2
  • linuxfoundation argo_continuous_delivery 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-77459 updated

argo-cd: github.com/argoproj/argo-cd/v3: github.com/argoproj/argo-cd/v2: argo-cd: AppProject restrictions bypassed by PreDelete/PostDelete resource hooks

  • Red Hat OpenShift GitOps 1.20 openshift-gitops-1/argocd-rhel9 1791184378
    fixed: vendor fix RHSA-2026:77273
  • Red Hat OpenShift GitOps 1.21 openshift-gitops-1/argocd-rhel9 1791252092
    fixed: vendor fix RHSA-2026:77269
  • Red Hat OpenShift GitOps 1.22 openshift-gitops-1/argocd-rhel9 1791192797
    fixed: vendor fix RHSA-2026:77267
  • Red Hat Openshift Data Foundation 4 odf4/odf-multicluster-rhel9-operator
    not affected: vulnerable code not in execute path
  • Red Hat OpenShift GitOps openshift-gitops-1/gitops-rhel9, openshift-gitops-1/argocd-agent-rhel9, openshift-gitops-1/gitops-rhel9-operator, openshift-gitops-1/argocd-image-updater-rhel9 Red Hat OpenShift GitOps 1.20 openshift-gitops-1/dex-rhel9 1791183962, openshift-gitops-1/gitops-rhel9 1791183847, openshift-gitops-1/must-gather-rhel9 1791183724, openshift-gitops-1/argocd-agent-rhel9 1791183980, openshift-gitops-1/argo-rollouts-rhel9 1791184750, openshift-gitops-1/console-plugin-rhel9 1791184352, +4 more Red Hat OpenShift GitOps 1.21 openshift-gitops-1/dex-rhel9 1791253159, openshift-gitops-1/gitops-rhel9 1791252015, openshift-gitops-1/must-gather-rhel9 1791253104, openshift-gitops-1/argocd-agent-rhel9 1791261215, openshift-gitops-1/argo-rollouts-rhel9 1791251919, openshift-gitops-1/console-plugin-rhel9 1791252544, +4 more Red Hat OpenShift GitOps 1.22 openshift-gitops-1/dex-rhel9 1791193725, openshift-gitops-1/gitops-rhel9 1791192820, openshift-gitops-1/must-gather-rhel9 1791192360, openshift-gitops-1/argocd-agent-rhel9 1791193074, openshift-gitops-1/argo-rollouts-rhel9 1791192808, openshift-gitops-1/console-plugin-rhel9 1791192905, +7 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
25 d ago

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OSV 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd/v2
>=2.10.0, <=2.14.21
>=2.10.0
 no fix listed
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
3.3.15
3.4.10
3.5.4
3.6.0-rc2
bitnami argo-cd
>=2.10.0, <3.3.15
>=3.4.0, <3.4.10
>=3.5.0, <3.5.4
3.3.15
3.4.10
3.5.4
go github.com/argoproj/argo-cd
all versions
 no fix listed

Affected products

  • argoproj argo-cd

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.