CVE-2026-45737 Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations
Attackers can extract Kubernetes Secret values from Argo CD diffs due to insufficient sanitization of annotations in ServerSideDiff mode.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-45737?
CVE-2026-45737 is a medium-severity vulnerability in Argoproj Argo Cd, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 3.2.0 until 3.2.12, 3.3.10, and 3.4.2, Argo CD ServerSideDiff can expose Kubernetes Secret values embedded in the kubectl.kubernetes.io/last-applied-configuration annotation because HideSecretData(target, live, ...) does not fully sanitize ResourceDiff.TargetState and LiveState predicted live Secret objects, allowing sensitive data, stringData, and annotations to appear in UI or CLI diffs. This issue is fixed in versions 3.2.12, 3.3.10, and 3.4.2.
Which versions are affected by CVE-2026-45737?
10 open source packages ship an affected version, including github.com/argoproj/argo-cd/v3, argo-cd and github.com/argoproj/argo-cd. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/argoproj/argo-cd/v3 Go | From 3.2.0 | 3.2.12, 3.3.10, 3.4.2 |
github.com/argoproj/argo-cd/v3 Go | From 3.2.0 | 3.2.12 |
github.com/argoproj/argo-cd/v3 Go | From 3.2.0 | 3.2.12 |
github.com/argoproj/argo-cd/v3 Go | From 3.3.0-rc1 | 3.3.10 |
github.com/argoproj/argo-cd/v3 Go | From 3.3.0-rc1 | 3.3.10 |
github.com/argoproj/argo-cd/v3 Go | From 3.4.0-rc1 | 3.4.2 |
4 more packages
github.com/argoproj/argo-cd/v3 Go | From 3.4.0-rc1 | 3.4.2 |
argo-cd Bitnami | From 3.2.0 | 3.2.12, 3.3.10, 3.4.2 |
github.com/argoproj/argo-cd Go | All versions | None |
github.com/argoproj/argo-cd/v2 Go | All versions | None |
Products include Argoproj Argo Cd.
How do I fix CVE-2026-45737?
Upgrade github.com/argoproj/argo-cd/v3 to a fixed version for your release line: 3.2.12, 3.3.10 or 3.4.2.
Is CVE-2026-45737 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45737 exists.
Other vulnerabilities in Argoproj Argo Cd
- CVE-2025-55190 Argo CD: Project API Token Exposes Repository Credentials
- CVE-2022-29165 Argo CD will blindly trust JWT claims if anonymous access is enabled
- CVE-2023-40029 Cluster secret might leak in cluster details page in Argo CD
- CVE-2022-24768 Improper access control allows admin privilege escalation in Argo CD
- CVE-2024-21652 Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
Sources
Also known as BIT-argo-cd-2026-45737, CLEANSTART-2026-DK90139, CLEANSTART-2026-GI96066, CLEANSTART-2026-PH23167, GHSA-rg3g-4rw9-gqrp, GO-2026-5618 and 16 more.