Argo-cd authenticated users can enumerate clusters by name

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2024-36106: 0.41% estimated exploitation activity in the next 30 days; percentile 35.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Patches A patch for this vulnerability has been released in the following Argo CD versions: v2.11.3 v2.10.12 v2.9.17 For more information If you have any questions or comments about this advisory: Open an issue in the Argo CD issue tracker or discussions Join us on Slack in channel #argo-cd Credits This vulnerability was found & reported by @crenshaw-dev (Michael Crenshaw) The Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue

Published by the source

6 Jun 2024, 19:04 UTC

Last modified by the source

6 Jun 2024, 19:04 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3cqf-953p-h5cp

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

# Patch Next advisory brief: CVE-2024-36106

Advisory: Argo-cd authenticated users can enumerate clusters by name
IDs: CVE-2024-36106, GHSA-3cqf-953p-h5cp
Record: https://patchnext.com/advisories/cve-2024-36106 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/argoproj/argo-cd 2.11.3, 2.10.12, 2.9.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd: affected >= 0.11.0, < 2.9.17; >= 2.10.0, < 2.10.12; >= 2.11.0, < 2.11.3; fixed in 2.9.17, 2.10.12, 2.11.3

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on 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://github.com/advisories/GHSA-3cqf-953p-h5cp (GitHub-reviewed advisory GHSA-3cqf-953p-h5cp lists affected ranges: Go github.com/argoproj/argo-cd >=0.11.0 =2.10.0 =2.11.0 <2.11.3)

Commands are suggestions: review each one before running it.