CVE-2025-23216: GO-2025-3433 - Argo CD does not scrub secret values from patch errors in github.com/argoproj/argo-cd

Quick answers

Is CVE-2025-23216 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-23216 being exploited in the wild.

How severe is CVE-2025-23216?

Low severity, with a CVSS score of 3.1, published 4 February 2025.

Which products and versions are affected?

github.com/argoproj/argo-cd (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.8.7; github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=0,fixed=2.11.13,introduced=2.12.0,fixed=2.12.10,introduced=2.13.0,fixed=2.13.4, SEMVER:introduced=2.13.0,fixed=2.13.4.

Is there a fix for CVE-2025-23216?

Yes. github.com/argoproj/argo-cd/v2 (Go): upgrade to 2.13.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2025-23216?

Check whether you run github.com/argoproj/argo-cd (Go) or github.com/argoproj/argo-cd/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• github.com/argoproj/argo-cd/v2 (Go): upgrade to 2.13.4 or later

  go get github.com/argoproj/argo-cd/v2@v2.13.4

Affected products

• github.com/argoproj/argo-cd (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.8.7
• github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=0,fixed=2.11.13,introduced=2.12.0,fixed=2.12.10,introduced=2.13.0,fixed=2.13.4, SEMVER:introduced=2.13.0,fixed=2.13.4

Identifiers

• CVE-2025-23216
• GHSA-47g2-qmh2-749v
• GO-2025-3433