Vulnerabilities in pkg:golang/github.com/argoproj/argo-cd/v2

PACKAGE
Advisory Identifier: GHSA-fmxq-cgp8-87wp
Advisory Summary

CVE-2026-77459 is a CRITICAL (CVSS 9.9) remote code execution vulnerability (CWE-863: Incorrect Authorization) affecting Argo CD libraries in the Go ecosystem. The issue involves appproject destination-namespace and resource restrictions bypassed by predelete/postdelete resource hooks. Remediation is available by upgrading affected packages to version 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2.

39 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/argoproj/argo-cd/v2

39 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/argoproj/argo-cd/v2. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-fmxq-cgp8-87wp CVE-2026-77459 CRITICAL Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
GHSA-j6cw-g6p4-7hch CVE-2026-55797 HIGH Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URL
GHSA-h98r-wv3h-fr38 CVE-2026-45738 HIGH Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation
GHSA-gpx4-37g2-c8pv CVE-2025-59538 HIGH Argo CD Unauthenticated Remote DoS via malformed Azure DevOps git.push webhook
GHSA-wp4p-9pxh-cgx2 CVE-2025-59537 HIGH argo-cd vulnerable unauthenticated DoS via malformed Gogs webhook payload
GHSA-f9gq-prrc-hrhc CVE-2025-59531 HIGH Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload
GHSA-g88p-r42r-ppp9 CVE-2025-55191 MODERATE Repository Credentials Race Condition Crashes Argo CD Server
GHSA-786q-9hcg-v9ff CVE-2025-55190 CRITICAL Argo CD's Project API Token Exposes Repository Credentials
GHSA-c8xw-vjgf-94hr CVE-2023-40025 HIGH Argo CD web terminal session doesn't expire
GHSA-g623-jcgg-mhmm CVE-2023-50726 MODERATE Users with `create` but not `override` privileges can perform local sync
GHSA-2hj5-g64g-fp6p CVE-2025-47933 CRITICAL Argo CD allows cross-site scripting on repositories page
GHSA-6p4m-hw2h-6gmw CVE-2023-22736 HIGH Controller reconciles apps outside configured namespaces when sharding is enabled
GHSA-47g2-qmh2-749v CVE-2025-23216 MODERATE Argo CD does not scrub secret values from patch errors
GHSA-x32m-mvfj-52xv CVE-2024-21652 CRITICAL Bypassing Brute Force Protection via Application Crash and In-Memory Data Loss
GHSA-mv6w-j4xc-qpfw CVE-2023-25163 MODERATE Argo CD leaks repository credentials in user-facing error messages and in logs
GHSA-h4w9-6x78-8vrj CVE-2022-31035 CRITICAL Argo CD's external URLs for Deployments can include JavaScript
GHSA-63qx-x74g-jcr7 CVE-2022-24348 HIGH Path traversal and dereference of symlinks in Argo CD
GHSA-qq5v-f4c3-395c CVE-2021-23347 MODERATE Possible XSS when using SSO with the CLI in github.com/argoproj/argo-cd/v2
GHSA-v8wx-v5jq-qhhw CVE-2024-41666 MODERATE The Argo CD web terminal session does not handle the revocation of user permissions properly
GHSA-jmvp-698c-4x3w CVE-2024-40634 HIGH Argo CD Unauthenticated Denial of Service (DoS) Vulnerability via /api/webhook Endpoint
GHSA-9766-5277-j5hr CVE-2024-31989 CRITICAL ArgoCD Vulnerable to Use of Risky or Missing Cryptographic Algorithms in Redis Cache
GHSA-jwv5-8mqv-g387 CVE-2024-28175 CRITICAL Cross-site scripting on application summary component
GHSA-6v85-wr92-q4p7 CVE-2024-21661 HIGH Denial of Service (DoS) Vulnerability Due to Unsafe Array Modification in Multi-threaded Environment
GHSA-9m6p-x4h2-6frq CVE-2024-32476 MODERATE Argo CD vulnerable to a Denial of Service via malicious jqPathExpressions in ignoreDifferences
GHSA-2gvw-w6fj-7m3c CVE-2024-31990 MODERATE Argo CD's API server does not enforce project sourceNamespaces
GHSA-jhwx-mhww-rgc3 CVE-2024-29893 MODERATE ArgoCD's repo server has Uncontrolled Resource Consumption vulnerability
GHSA-2vgg-9h6w-m454 CVE-2024-21662 MODERATE Bypassing Rate Limit and Brute Force Protection Using Cache Overflow
GHSA-92mw-q256-5vwg CVE-2024-22424 HIGH github.com/argoproj/argo-cd Cross-Site Request Forgery vulnerability
GHSA-6jqw-jwf5-rp8h CVE-2023-40026 MODERATE Path traversal allows leaking out-of-bound Helm charts from Argo CD repo-server
GHSA-g687-f2gx-6wm8 CVE-2023-40584 MODERATE Argo CD repo-server Denial of Service vulnerability
GHSA-fwr2-64vr-xv9m CVE-2023-40029 CRITICAL Argo CD cluster secret might leak in cluster details page
GHSA-96jv-vj39-x4j6 CVE-2022-1025 HIGH Argo CD improper access control bug can allow malicious user to escalate privileges to admin level
GHSA-2q5c-qw9c-fmvq CVE-2022-41354 MODERATE Argo CD authenticated but unauthorized users may enumerate Application names via the API
GHSA-jhqp-vf4w-rpwq CVE-2022-31016 MODERATE DoS through large manifest files in Argo CD
GHSA-q4w5-4gq2-98vm CVE-2022-31036 MODERATE Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server
GHSA-2m7h-86qq-fp4v CVE-2022-31034 HIGH Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params
GHSA-r642-gv9p-2wjj CVE-2022-29165 CRITICAL Argo CD will blindly trust JWT claims if anonymous access is enabled
GHSA-xmg8-99r8-jc2j CVE-2022-24905 MODERATE Login screen allows message spoofing if SSO is enabled
GHSA-6gcg-hp2x-q54h CVE-2022-24904 MODERATE Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server

CVE-2026-77459 at a Glance

CVE Identifier CVE-2026-77459
GHSA Identifier GHSA-fmxq-cgp8-87wp
Severity CRITICAL
CVSS v3.1 Base Score 9.9
CWE Classification CWE-863: Incorrect Authorization
Affected Product Argo CD
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-77459

To remediate this vulnerability, upgrade all affected Argo CD dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/argoproj/argo-cd/v2 fixed: Latest secure release
Upgrade github.com/argoproj/argo-cd/v2 to Latest secure release
github.com/argoproj/argo-cd/v3 fixed: 3.3.15
Upgrade github.com/argoproj/argo-cd/v3 to 3.3.15
github.com/argoproj/argo-cd/v3 fixed: 3.4.10
Upgrade github.com/argoproj/argo-cd/v3 to 3.4.10
github.com/argoproj/argo-cd/v3 fixed: 3.5.4
Upgrade github.com/argoproj/argo-cd/v3 to 3.5.4
github.com/argoproj/argo-cd/v3 fixed: 3.6.0-rc2
Upgrade github.com/argoproj/argo-cd/v3 to 3.6.0-rc2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/argoproj/argo-cd/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-77459, inspect your project dependencies for Argo CD:

inspect dependencies for github.com/argoproj/argo-cd/v2

Analyze the terminal output to locate any version of Argo CD in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.3.15), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Argo CD, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Argo CD checks an Application's AppProject before it creates resources during a sync. That check covers destination namespaces and servers, cluster-scoped resource allow and deny lists, and namespaced resource allow and deny lists, including resource names. PreDelete and PostDelete hooks skip it. When the Application is deleted, Argo CD creates those hooks with the application-controller's credentials on the destination cluster. All versions from v2.10.0 onward are affected, including every currently supported release. v2.9.22 and earlier are not. PostDelete hooks were introduced in [dcc17f70bf](https://github.com/argoproj/argo-cd/commit/dcc17f70bf7db973fe480b8b613189b2c5ac4b4b) (2023-12-18, [#16595](https://github.com/argoproj/argo-cd/pull/16595)) and first released in v2.10.0. That creation path has never applied the project check. PreDelete hooks, added in [3bf3d8a212](https://github.com/argoproj/argo-cd/commit/3bf3d8a2124e772ac651f3fd42375c4e9b8008af) (2025-12-05, [#22288](https://github.com/argoproj/argo-cd/pull/22288)) and first released in v3.3.0, use the same path. v3.2.12 and earlier do not have PreDelete hooks. PreSync, Sync, PostSync, and SyncFail hooks still go through the project check. A user who can push to the Git repository an Application syncs from can commit a hook whose namespace, group, kind, or name the AppProject would refuse on sync. The controller adds the delete finalizer when it sees the hook, and the Application stays Synced until someone deletes it. Deleting the Application creates the hook. What that can reach is bounded by the application-controller's access to the destination cluster. In a typical install that access is broad, so a tenant can create a cluster-scoped object such as a `ClusterRoleBinding`, or an object in a namespace the project does not allow. A hook with no deletion policy is removed after it succeeds. A deletion policy that does not remove the hook on success leaves the object in the cluster. A hook such as a Job can create further objects that Argo CD does not clean up. ### Patches A patch for this vulnerability has been released in the following Argo CD versions: * v3.6.0-rc2 * v3.5.4 * v3.4.10 * v3.3.15 The fix applies the same AppProject destination and resource checks used on sync before creating a PreDelete or PostDelete hook. Argo CD 2.x and 3.0 through 3.2 are out of support and will not receive a patch. Upgrade to a patched 3.3 or newer release. ### Workarounds There is no configuration setting that applies the project check to delete hooks while those hooks stay in use. * Do not grant untrusted users write access to Git repositories that back Applications in restrictive AppProjects. * Limit who can delete Applications. Deletion is what runs PreDelete and PostDelete hooks. * Tighten the application-controller's Kubernetes access so a hook cannot reach sensitive namespaces or APIs. ### Credits The Argo CD team would like to thank @RealFakeAccount, @AdamKorcz, @0xshylines, @thevilledev, @HenriWilliams, @cherez0ff, @ARSB1, and @zwindler for responsibly disclosing this issue according to our [security reporting guidelines](https://github.com/argoproj/argo-cd/blob/master/SECURITY.md#reporting-a-vulnerability). ### References * PostDelete introducing commit: [dcc17f70bf7db973fe480b8b613189b2c5ac4b4b](https://github.com/argoproj/argo-cd/commit/dcc17f70bf7db973fe480b8b613189b2c5ac4b4b) ([#16595](https://github.com/argoproj/argo-cd/pull/16595)), first released in v2.10.0 * PreDelete introducing commit: [3bf3d8a2124e772ac651f3fd42375c4e9b8008af](https://github.com/argoproj/argo-cd/commit/3bf3d8a2124e772ac651f3fd42375c4e9b8008af) ([#22288](https://github.com/argoproj/argo-cd/pull/22288)), first released in v3.3.0 * [AppProject specification](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/) * [Resource hooks](https://argo-cd.readthedocs.io/en/stable/user-guide/resource_hooks/) ### For more information * Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions) * Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd

CVE-2026-77459 Affected Argo CD Versions

5 component(s)
Fixed Versions:
3.3.153.4.103.5.43.6.0-rc2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/argoproj/argo-cd/v2
Go
≥ 2.10.0
≤ 2.14.21
github.com/argoproj/argo-cd/v3
Go
≥ 3.0.0
< 3.3.15
3.3.15
github.com/argoproj/argo-cd/v3
Go
≥ 3.4.0
< 3.4.10
3.4.10
github.com/argoproj/argo-cd/v3
Go
≥ 3.5.0
< 3.5.4
3.5.4
github.com/argoproj/argo-cd/v3
Go
≥ 3.6.0-rc1
< 3.6.0-rc2
3.6.0-rc2

References

Frequently Asked Questions

What is CVE-2026-77459?
CVE-2026-77459 is a security vulnerability in Argo CD involving AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks under CWE-863: Incorrect Authorization.
Which Argo CD versions are affected?
Affected versions include releases prior to 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2 across affected packages: github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd/v3.
What version fixes CVE-2026-77459?
Upgrading to 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/argoproj/argo-cd/v2 affected?
Yes, github.com/argoproj/argo-cd/v2 is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
Is github.com/argoproj/argo-cd/v3 affected?
Yes, github.com/argoproj/argo-cd/v3 is affected in releases prior to 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2. Upgrade your dependency to 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2 or later.
What is the CVSS score of CVE-2026-77459?
CVE-2026-77459 has a CVSS v3.1 base score of 9.9 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-77459?
CVE-2026-77459 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2026-77459?
Run the dependency tree command: 'inspect dependencies for github.com/argoproj/argo-cd/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fmxq-cgp8-87wp",
  "modified" : "2026-10-15T20:19:31Z",
  "published" : "2026-10-15T20:19:31Z",
  "aliases" : [ "CVE-2026-77459" ],
  "summary" : "Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks",
  "details" : "### Impact\n\nArgo CD checks an Application's AppProject before it creates resources during a sync. That check covers destination namespaces and servers, cluster-scoped resource allow and deny lists, and namespaced resource allow and deny lists, including resource names. PreDelete and PostDelete hooks skip it. When the Application is deleted, Argo CD creates those hooks with the application-controller's credentials on the destination cluster.\n\nAll versions from v2.10.0 onward are affected, including every currently supported release. v2.9.22 and earlier are not. PostDelete hooks were introduced in [dcc17f70bf](https://github.com/argoproj/argo-cd/commit/dcc17f70bf7db973fe480b8b613189b2c5ac4b4b) (2023-12-18, [#16595](https://github.com/argoproj/argo-cd/pull/16595)) and first released in v2.10.0. That creation path has never applied the project check. PreDelete hooks, added in [3bf3d8a212](https://github.com/argoproj/argo-cd/commit/3bf3d8a2124e772ac651f3fd42375c4e9b8008af) (2025-12-05, [#22288](https://github.com/argoproj/argo-cd/pull/22288)) and first released in v3.3.0, use the same path. v3.2.12 and earlier do not have PreDelete hooks. PreSync, Sync, PostSync, and SyncFail hooks still go through the project check.\n\nA user who can push to the Git repository an Application syncs from can commit a hook whose namespace, group, kind, or name the AppProject would refuse on sync. The controller adds the delete finalizer when it sees the hook, and the Application stays Synced until someone deletes it. Deleting the Application creates the hook. What that can reach is bounded by the application-controller's access to the destination cluster. In a typical install that access is broad, so a tenant can create a cluster-scoped object such as a `ClusterRoleBinding`, or an object in a namespace the project does not allow. A hook with no deletion policy is removed after it succeeds. A deletion policy that does not remove the hook on success leaves the object in the cluster. A hook such as a Job can create further objects that Argo CD does not clean up.\n\n### Patches\n\nA patch for this vulnerability has been released in the following Argo CD versions:\n\n* v3.6.0-rc2\n* v3.5.4\n* v3.4.10\n* v3.3.15\n\nThe fix applies the same AppProject destination and resource checks used on sync before creating a PreDelete or PostDelete hook.\n\nArgo CD 2.x and 3.0 through 3.2 are out of support and will not receive a patch. Upgrade to a patched 3.3 or newer release.\n\n### Workarounds\n\nThere is no configuration setting that applies the project check to delete hooks while those hooks stay in use.\n\n* Do not grant untrusted users write access to Git repositories that back Applications in restrictive AppProjects.\n* Limit who can delete Applications. Deletion is what runs PreDelete and PostDelete hooks.\n* Tighten the application-controller's Kubernetes access so a hook cannot reach sensitive namespaces or APIs.\n\n### Credits\n\nThe Argo CD team would like to thank @RealFakeAccount, @AdamKorcz, @0xshylines, @thevilledev, @HenriWilliams, @cherez0ff, @ARSB1, and @zwindler for responsibly disclosing this issue according to our [security reporting guidelines](https://github.com/argoproj/argo-cd/blob/master/SECURITY.md#reporting-a-vulnerability).\n\n### References\n\n* PostDelete introducing commit: [dcc17f70bf7db973fe480b8b613189b2c5ac4b4b](https://github.com/argoproj/argo-cd/commit/dcc17f70bf7db973fe480b8b613189b2c5ac4b4b) ([#16595](https://github.com/argoproj/argo-cd/pull/16595)), first released in v2.10.0\n* PreDelete introducing commit: [3bf3d8a2124e772ac651f3fd42375c4e9b8008af](https://github.com/argoproj/argo-cd/commit/3bf3d8a2124e772ac651f3fd42375c4e9b8008af) ([#22288](https://github.com/argoproj/argo-cd/pull/22288)), first released in v3.3.0\n* [AppProject specification](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/)\n* [Resource hooks](https://argo-cd.readthedocs.io/en/stable/user-guide/resource_hooks/)\n\n### For more information\n\n* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)\n* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.10.0"
      }, {
        "last_affected" : "2.14.21"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.3.15"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.4.0"
      }, {
        "fixed" : "3.4.10"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.5.0"
      }, {
        "fixed" : "3.5.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.6.0-rc1"
      }, {
        "fixed" : "3.6.0-rc2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/security/advisories/GHSA-fmxq-cgp8-87wp"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-77459"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/commit/1149cdc6e932208c4402183cc3d7b7485239940c"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/commit/4bc8085b0a6d2296b849539d3d09fc7be7a4a511"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/commit/7f0a05834b05103d69d7c150e1ee36541b314696"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/commit/d5dd7019ee65be8895133fe4df554e28074242c4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/argoproj/argo-cd"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/releases/tag/v3.3.15"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/releases/tag/v3.4.10"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/releases/tag/v3.5.4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/releases/tag/v3.6.0-rc2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-15T20:19:31Z",
    "nvd_published_at" : "2026-10-13T17:17:46Z"
  }
}