Argo CD cluster secret might leak in cluster details page

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:L

EPSS

• CVE-2023-40029: 1.20% estimated exploitation activity in the next 30 days; percentile 68.12 (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 Argo CD Cluster secrets might be managed declaratively using Argo CD / kubectl apply. As a result, the full secret body is stored inkubectl.kubernetes.io/last-applied-configuration annotation. https://github.com/argoproj/argo-cd/pull/7139 introduced the ability to manage cluster labels and annotations. Since clusters are stored as secrets it also exposes the kubectl.kubernetes.io/last-applied-configuration annotation which includes full secret body. In order to view the cluster annotations via the Argo CD API, the user must have clusters, get RBAC access. Note: In many cases, cluster secrets do not contain any actually-secret information. But sometimes, as in bearer-token auth, the contents might be very sensitive. Patches The bug has been patched in the following versions: 2.8.3 2.7.14 2.6.15 Workarounds Update/Deploy cluster secret with server-side-apply flag which does not use or rely on kubectl.kubernetes.io/last-applied-configuration annotation. Note: annotation for…

Published by the source

11 Sep 2023, 12:59 UTC

Last modified by the source

5 Nov 2023, 05:01 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fwr2-64vr-xv9m

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

# Patch Next advisory brief: CVE-2023-40029

Advisory: Argo CD cluster secret might leak in cluster details page
IDs: CVE-2023-40029, GHSA-fwr2-64vr-xv9m
Record: https://patchnext.com/advisories/cve-2023-40029 (revision 1, source checked 26 Oct 2026, 14:59 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: Vendor fix available; fixed versions by package: github.com/argoproj/argo-cd/v2 2.8.3, 2.7.14, 2.6.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected >= 2.2.0, < 2.6.15; >= 2.7.0, < 2.7.14; >= 2.8.0, < 2.8.3; fixed in 2.8.3, 2.7.14, 2.6.15

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2: 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/v2.
- 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-fwr2-64vr-xv9m (GitHub-reviewed advisory GHSA-fwr2-64vr-xv9m lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.2.0 =2.7.0 =2.8.0 <2.8.3)

Commands are suggestions: review each one before running it.