NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

Argo CD cluster secret might leak in cluster details pageGHSA-fwr2-64vr-xv9m

CRITICALFix: argoproj/argo-cd#7139

GHSA-fwr2-64vr-xv9m is a critical-severity (CVSS 9.9) Information Exposure vulnerability in github.com/argoproj/argo-cd/v2. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/argoproj/argo-cd/v2 — see the affected versions and patch details below.

Also known asBIT-argo-cd-2023-40029CVE-2023-40029GO-2023-2049
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fwr2-64vr-xv9m.

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk
0.42%0.84%1.27%1.70%0.9%1.2%May 26Aug 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 existing secrets will require manual removal.

For more information

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/argoproj/argo-cd/v2≥ 2.2.0&&< 2.6.152.6.15go get github.com/argoproj/argo-cd/v2@v2.6.15
🐹Gogithub.com/argoproj/argo-cd/v2≥ 2.7.0&&< 2.7.142.7.14go get github.com/argoproj/argo-cd/v2@v2.7.14
🐹Gogithub.com/argoproj/argo-cd/v2≥ 2.8.0&&< 2.8.32.8.3go get github.com/argoproj/argo-cd/v2@v2.8.3

Affected Products

1 product · 3 configurations
Application
argo cdargoproj
≥ 2.8.0 && < 2.8.3
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Argo CD is a declarative continuous deployment for Kubernetes. Argo CD C…

github.comNVDSep 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-cd/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/argoproj/argo-cd/v2 to 2.6.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fwr2-64vr-xv9m is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical
Workaround published by Red Hat
Update/deploy the cluster secret with the`server-side-apply` flag, which does not use or rely on the `kubectl.kubernetes.io/last-applied-configuration` <http://kubectl.kubernetes.io/last-applied-configuration> annotation. Note: Annotation for existing secrets will require manual removal.
Source: Red Hat security advisory for GHSA-fwr2-64vr-xv9m (CC BY 4.0)
ProductFixed inAdvisory
Red Hat OpenShift GitOps 1.8openshift-gitops-1/argocd-rhel8:v1.8.5-1RHSA-2023:5030
Red Hat OpenShift GitOps 1.9openshift-gitops-1/argocd-rhel8:v1.9.2-2RHSA-2023:5029

Frequently Asked Questions

### Impact Argo CD Cluster secrets might be managed declaratively using Argo CD / kubectl apply. As a result, the full secret body is stored in`kubectl.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
O3 Security · Impact-Aware SCA

Is GHSA-fwr2-64vr-xv9m in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Argo CD cluster secret might leak in cluster details page