# 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. - **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Jul 2026 - **Updated:** 16 Jul 2026 - **Also known as:** BIT-argo-cd-2026-45737, CLEANSTART-2026-DK90139, CLEANSTART-2026-GI96066, CLEANSTART-2026-PH23167, GHSA-rg3g-4rw9-gqrp, GO-2026-5618, MINI-2hcf-wqgf-4m2p, MINI-5485-hcj3-87g2, MINI-72cm-mgh4-3r57, MINI-76hf-q5pf-hr7v, MINI-9437-p5pv-3556, MINI-cg8g-685c-7x7p, MINI-fcg6-385j-cvcq, MINI-hj3v-gw86-q68h, MINI-p659-vcr7-q8r3, MINI-p6hm-23r4-74pr, MINI-ppgc-j463-xvpx, MINI-qfhw-6jhx-fjq5, MINI-qr7m-rjfc-c5x9, MINI-wqx2-5qh4-652m, MINI-xq8v-p53p-pmv3, MINI-xrf5-2xwg-567v ## 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. Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## 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 | Ecosystem | 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 | | `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: 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](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-45737 and fix it if it is affected. What it is: 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. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45737 exists. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v3 (Go): affected from 3.2.0; fixed in 3.2.12, 3.3.10, 3.4.2 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.2.0; fixed in 3.2.12 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.2.0; fixed in 3.2.12 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.3.0-rc1; fixed in 3.3.10 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.3.0-rc1; fixed in 3.3.10 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.4.0-rc1; fixed in 3.4.2 - github.com/argoproj/argo-cd/v3 (Go): affected from 3.4.0-rc1; fixed in 3.4.2 - argo-cd (Bitnami): affected from 3.2.0; fixed in 3.2.12, 3.3.10, 3.4.2 - github.com/argoproj/argo-cd (Go): affected all versions; no fix listed - github.com/argoproj/argo-cd/v2 (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-45737/ (Markdown: https://insights.sbomify.com/CVE-2026-45737/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45737 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45737 - OSV: https://osv.dev/vulnerability/CVE-2026-45737 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-45737/ Summaries are generated and may contain mistakes; the official description above is the record.