CVE-2024-36106 | Argo CD allows authenticated users to enumerate clusters by name

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. It’s possible for authenticated users to enumerate clusters by name by inspecting error messages. It’s also possible to enumerate the names of projects with project-scoped clusters if you know the names of the clusters. This vulnerability is fixed in 2.11.3, 2.10.12, and 2.9.17.

Published: 2024-06-06 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-36106 is rated Low Risk (28.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.41%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-36106

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.64% 0.41% -0.23%
2 2025-11-21 0.33% 0.64% +0.31%
3 2025-11-18 — 0.33% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-36106

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [email protected]
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [email protected]

Weakness enumeration for CVE-2024-36106

GitHub Security Advisory for CVE-2024-36106

GHSA-3cqf-953p-h5cp · Severity: medium · Ecosystem: go — Argo-cd authenticated users can enumerate clusters by name

OS Trackers for CVE-2024-36106

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2024-36106

Affected software / configurations for CVE-2024-36106

Vendor Product Version Raw CPE
argoproj argo_cd > 0.11.0, < 2.9.17 cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*
argoproj argo_cd >= 2.10.0, < 2.10.12 cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*
argoproj argo_cd >= 2.11.0, < 2.11.3 cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*

References for CVE-2024-36106

cvelogic Threat Intelligence