SecOps SignalSecurity Intelligence Workspace
Collection Degraded30 / 46 Sources HealthyPublic Intel Only
Vulnerabilities/CVE-2026-77459Public Intelligence Dossier
Source: Source type: NVD · Limited verification•Last verified: •Collection Degraded
CVE-2026-77459Unknown / EvaluatingCRITICAL (raw)CVSS 9.9CWE-863

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes

Published: 13 Oct 2026•Last updated: 16 Oct 2026, 09:30 PM IST•Source identifier: security-advisories@github.com
Dossier completeness: source-provided sections 1 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
9.9CRITICAL (raw)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Metric sourcesecurity-advisories@github.com
EPSS probability
0.7%0.007
Percentile53rd
Weakness type
CWE-863
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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.

SOC priority

High Severity / Review

Actively exploited

Unknown

Publicly disclosed

Unknown

Risk basis: SOC ecosystem technology relevance; CRITICAL severity; Critical CVSS without confirmed KEV exploitation

Affected Products & Remediation

0 source-backed products
Affected products and versions (source)Not provided by source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

Not provided by source

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched authorization-bypass (CWE-863)

Exposure

  1. Locate affected authorization controls and verify deployed versions.Telemetry: Application inventory · The source must identify the affected control. · Rule authorization-bypass

Exploitation evidence

  1. Review privileged operations performed by unexpected users on affected deployments.Telemetry: Application audit logs · Authorization anomalies can support a targeted hunt. · Rule authorization-bypass

Response

  1. Confirm the vendor mitigation and recheck access decisions.Telemetry: Application audit logs · Access testing verifies the local fix. · Rule authorization-bypass

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
security-advisories@github.com
Record status · verification
UPDATED · NVD API
CPE
Unknown
Detection Hunting Query

— No published hunting query names this record. Browse community and library queries instead.

Correlated briefings

— No published briefing references this CVE

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.