CVE-2026-77459

CRITICALPre-NVD 9.99.9
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.9
EG Score
9.9CRITICALlow confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
The EG Score, 9.9 of 10.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 13, 2026

Last Modified

October 13, 2026

Advisory Details (9)

Auto-updated Oct 13, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available

v3.6.0-rc2

Patch available: argoproj/argo-cd v3.6.0-rc2 (pre-release)

https://github.com/argoproj/argo-cd/releases/tag/v3.6.0-rc2
GitHub release Patch Available

v3.5.4

Patch available: argoproj/argo-cd v3.5.4

https://github.com/argoproj/argo-cd/releases/tag/v3.5.4
GitHub release Patch Available

v3.4.10

Patch available: argoproj/argo-cd v3.4.10

https://github.com/argoproj/argo-cd/releases/tag/v3.4.10
GitHub release Patch Available

v3.3.15

Patch available: argoproj/argo-cd v3.3.15

https://github.com/argoproj/argo-cd/releases/tag/v3.3.15
GitHub commit

commit d5dd7019ee65 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit d5dd7019ee65 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/d5dd7019ee65be8895133fe4df554e28074242c4
GitHub commit

commit 7f0a05834b05 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit 7f0a05834b05 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/7f0a05834b05103d69d7c150e1ee36541b314696
GitHub commit

commit 4bc8085b0a6d (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit 4bc8085b0a6d — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/4bc8085b0a6d2296b849539d3d09fc7be7a4a511
GitHub commit

commit 1149cdc6e932 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit 1149cdc6e932 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/1149cdc6e932208c4402183cc3d7b7485239940c
GitHub advisoryMentions a patch (unverified)

AppProject restrictions bypassed by PreDelete/PostDelete resource hooks · Advisory · argoproj/argo-cd · GitHub

https://github.com/argoproj/argo-cd/security/advisories/GHSA-fmxq-cgp8-87wp

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 3× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 17:25 UTCEG score recompute
  2. 2026-10-13 16:39 UTCEG score recomputeFirst assessed: 9.9 CRITICAL
  3. 2026-10-13 16:39 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-77459?
CVE-2026-77459 is a critical-severity vulnerability; its CVE record was published on October 13, 2026. 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…
When was the CVE record for CVE-2026-77459 published?
The CVE record for CVE-2026-77459 was published on October 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-77459?
CVE-2026-77459 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-77459?
A fix for CVE-2026-77459 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-77459

Explore →

Is Your Infrastructure Affected by CVE-2026-77459?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.