cve.bz

CVE-2026-77459 argoproj argo-cd: Incorrect Authorization

9.9 criticalEPSS 0.5%Fix available

Critical (9.9) in argoproj argo-cd. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/argoproj/argo-cd/v3 3.3.15, 3.4.10, 3.5.4.

On this page
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.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-77459 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77459?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77459?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77459 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
argoproj argo-cd>= 2.10.0, <= 2.14.21
argoproj argo-cd>= 3.0.0, < 3.3.15
argoproj argo-cd>= 3.4.0, < 3.4.10
argoproj argo-cd>= 3.5.0, < 3.5.4
argoproj argo-cd>= 3.6.0-rc1, < 3.6.0-rc2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fmxq-cgp8-87wpGogithub.com/argoproj/argo-cd/v2>=2.10.0 <=2.14.21no fix published
GHSA-fmxq-cgp8-87wpGogithub.com/argoproj/argo-cd/v3>=3.0.0 <3.3.153.3.15
GHSA-fmxq-cgp8-87wpGogithub.com/argoproj/argo-cd/v3>=3.4.0 <3.4.103.4.10
GHSA-fmxq-cgp8-87wpGogithub.com/argoproj/argo-cd/v3>=3.5.0 <3.5.43.5.4
GHSA-fmxq-cgp8-87wpGogithub.com/argoproj/argo-cd/v3>=3.6.0-rc1 <3.6.0-rc23.6.0-rc2
GO-2026-6784Gogithub.com/argoproj/argo-cdall versionsno fix published
GO-2026-6784Gogithub.com/argoproj/argo-cd/v2>=2.10.0no fix published
GO-2026-6784Gogithub.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

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1SUSE-SU-2026:24730-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat rates this vulnerability as Important because it permits multi-tenant boundary bypasses that can lead to cluster-wide privilege escalation, though exploitation requires existing write privileges to a linked source repository. In Red Hat OpenShift GitOps installations relying on AppProjects to enforce namespace and resource isolation, PreDelete and PostDelete hooks bypass project admission validation. When an application is deleted, the application-controller executes these hooks using its high-privilege credentials, allowing unauthorized workloads or permissions to be created outside the tenant boundary.

ProductPackageStateAdvisory
Red Hat OpenShift GitOps 1.20openshift-gitops-1/argocd-rhel9:1791184378Fixed 2026-10-07RHSA-2026:77273
Red Hat OpenShift GitOps 1.21openshift-gitops-1/argocd-rhel9:1791252092Fixed 2026-10-07RHSA-2026:77269
Red Hat OpenShift GitOps 1.22openshift-gitops-1/argocd-rhel9:1791192797Fixed 2026-10-07RHSA-2026:77267
Red Hat Openshift Data Foundation 4odf4/odf-multicluster-rhel9-operatorNot affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-agent-rhel9Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-image-updater-rhel9Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/gitops-rhel9Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/gitops-rhel9-operatorNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-77459.

References

Check your stackJSON