# CVE-2025-23216: Argo CD does not scrub secret values from patch errors > Attackers with repository write access can expose secret values in error messages and diff views, allowing read-access users to view sensitive data. - **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Jan 2025 - **Updated:** 12 Feb 2025 - **Also known as:** BIT-argo-cd-2025-23216, GHSA-47g2-qmh2-749v, GO-2025-3433 ## What is CVE-2025-23216? CVE-2025-23216 is a medium-severity vulnerability in Argoproj Argo Cd, published on 30 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. A vulnerability was discovered in Argo CD that exposed secret values in error messages and the diff view when an invalid Kubernetes Secret resource was synced from a repository. The vulnerability assumes the user has write access to the repository and can exploit it, either intentionally or unintentionally, by committing an invalid Secret to repository and triggering a Sync. Once exploited, any user with read access to Argo CD can view the exposed secret data. The vulnerability is fixed in v2.13.4, v2.12.10, and v2.11.13. Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2025-23216? 11 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2, argo-cd and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.11.13, 2.12.10, 2.13.4 | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.11.13 | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.11.13 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.12.0 | 2.12.10 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.12.0 | 2.12.10 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.13.0 | 2.13.4 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.13.0 | 2.13.4 | | `argo-cd` | Bitnami | All versions | 2.13.4 | | `github.com/argoproj/argo-cd` | Go | All versions | None | | `github.com/argoproj/argo-cd` | Go | All versions to 1.8.7 | None | | `github.com/argoproj/argo-cd` | Go | All versions to 1.8.7 | None | Products: Argoproj Argo Cd. ## How do I fix CVE-2025-23216? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.11.13, 2.12.10 or 2.13.4. ## Is CVE-2025-23216 being exploited? There is no known exploitation of CVE-2025-23216 in the wild and no public exploit code. ## 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-2025-23216 and fix it if it is affected. What it is: CVE-2025-23216 is a medium-severity vulnerability in Argoproj Argo Cd, published on 30 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-23216 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.11.13, 2.12.10, 2.13.4 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.11.13 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.11.13 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.12.0; fixed in 2.12.10 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.12.0; fixed in 2.12.10 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.13.0; fixed in 2.13.4 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.13.0; fixed in 2.13.4 - argo-cd (Bitnami): affected all versions; fixed in 2.13.4 - github.com/argoproj/argo-cd (Go): affected all versions; no fix listed - github.com/argoproj/argo-cd (Go): affected all versions up to 1.8.7; no fix listed - github.com/argoproj/argo-cd (Go): affected all versions up to 1.8.7; 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-2025-23216/ (Markdown: https://insights.sbomify.com/CVE-2025-23216/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23216 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23216 - OSV: https://osv.dev/vulnerability/CVE-2025-23216 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-23216/ Summaries are generated and may contain mistakes; the official description above is the record.