Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.9amended

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

CVE-2026-77459GHSA-fmxq-cgp8-87wp

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/argoproj/argo-cd/v2

    Affected
    >= 2.10.0, <= 2.14.21
    Fixed in
    no fixed version recorded

  • Go github.com/argoproj/argo-cd/v3

    Affected
    >= 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
    Fixed in
    3.5.4, 3.3.15, 3.6.0-rc2, 3.4.10

  • Go github.com/argoproj/argo-cd

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-77459: 0.50% estimated exploitation activity in the next 30 days; percentile 42.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 (2023-12-18, #16595) and first released in v2.10.0. That creation path has never applied the project check. PreDelete hooks, added in 3bf3d8a212 (2025-12-05, #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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-fmxq-cgp8-87wp

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6784

  3. Revision 1 · created ·

    Published from osv record GHSA-fmxq-cgp8-87wp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-77459

Advisory: Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
IDs: CVE-2026-77459, GHSA-fmxq-cgp8-87wp
Record: https://patchnext.com/advisories/cve-2026-77459 (revision 3, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-cd/v3 3.6.0-rc2, 3.5.4, 3.4.10, 3.3.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected >= 2.10.0, <= 2.14.21
- Go github.com/argoproj/argo-cd/v3: affected >= 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; fixed in 3.5.4, 3.3.15, 3.6.0-rc2, 3.4.10
- Go github.com/argoproj/argo-cd: affected every version

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager.
- Go github.com/argoproj/argo-cd/v3: check the installed version with your package manager.
- Go github.com/argoproj/argo-cd: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd/v3, github.com/argoproj/argo-cd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6784 (OSV record GO-2026-6784 lists affected ranges: Go github.com/argoproj/argo-cd >=0; Go github.com/argoproj/argo-cd/v2 >=2.10.0; Go github.com/argoproj/argo-cd/v3 >=3.0.0 =3.4.0 =3.5.0 =3.6.0-rc1 <3.6.0-rc2 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-fmxq-cgp8-87wp (OSV record GHSA-fmxq-cgp8-87wp lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.10.0 =3.0.0 =3.4.0 =3.5.0 =3.6.0-rc1 <3.6.0-rc2 (fixed))
- Verified: https://github.com/advisories/GHSA-fmxq-cgp8-87wp (GitHub-reviewed advisory GHSA-fmxq-cgp8-87wp lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.10.0 =3.0.0 =3.4.0 =3.5.0 =3.6.0-rc1 <3.6.0-rc2)

Commands are suggestions: review each one before running it.

Loading voting…