Argo CD does not scrub secret values from patch errors
CVE-2025-23216GHSA-47g2-qmh2-749v
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/argoproj/argo-cd/v2
- Affected
- >= 2.13.0, < 2.13.4>= 2.12.0, < 2.12.10< 2.11.13
- Fixed in
- 2.11.13, 2.13.4, 2.12.10
Go github.com/argoproj/argo-cd
- Affected
- <= 1.8.7
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-47g2-qmh2-749v lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.13.0 =2.12.0 =0 =0 <=1.8.7
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
- EPSS
- CVE-2025-23216: 0.47% estimated exploitation activity in the next 30 days; percentile 41.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact 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. Patches A patch for this vulnerability is available in the following Argo CD versions: - v2.13.4 - v2.12.10 - v2.11.13 Workarounds There is no workaround other than upgrading. References Fixed with commit https://github.com/argoproj/argo-cd/commit/6f5537bdf15ddbaa0f27a1a678632ff0743e4107 & https://github.com/argoproj/gitops-engine/commit/7e21b91e9d0f64104c8a661f3f390c5e6d73ddca
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-47g2-qmh2-749v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-23216 Advisory: Argo CD does not scrub secret values from patch errors IDs: CVE-2025-23216, GHSA-47g2-qmh2-749v Record: https://patchnext.com/advisories/cve-2025-23216 (revision 1, source checked 26 Oct 2026, 15:09 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-cd/v2 2.13.4, 2.12.10, 2.11.13. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/argoproj/argo-cd/v2: affected >= 2.13.0, < 2.13.4; >= 2.12.0, < 2.12.10; < 2.11.13; fixed in 2.11.13, 2.13.4, 2.12.10 - Go github.com/argoproj/argo-cd: affected <= 1.8.7 ## Suggested inspection (read-only) - Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager. - Go github.com/argoproj/argo-cd: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd. - 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-47g2-qmh2-749v (GitHub-reviewed advisory GHSA-47g2-qmh2-749v lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.13.0 =2.12.0 =0 =0 <=1.8.7) Commands are suggestions: review each one before running it.
Loading voting…