Argo CD GitOps Engine does not scrub secret values from patch errors

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

No dated EPSS signal available.

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. Resources Fixed with commit https://github.com/argoproj/argo-cd/commit/6f5537bdf15ddbaa0f27a1a678632ff0743e4107 & https://github.com/argoproj/gitops-engine/commit/7e21b91e9d0f64104c8a661f3f390c5e6d73ddca

Published by the source

30 Jan 2025, 17:51 UTC

Last modified by the source

20 Dec 2025, 03:10 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-274v-mgcv-cm8j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-274v-mgcv-cm8j

Advisory: Argo CD GitOps Engine does not scrub secret values from patch errors
IDs: GHSA-274v-mgcv-cm8j
Record: https://patchnext.com/advisories/ghsa-274v-mgcv-cm8j (revision 1, source checked 26 Oct 2026, 15:13 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/gitops-engine 0.7.1-0.20250129155113-4c6e03c463141. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/gitops-engine: affected >= 0.7.2, <= 0.7.3; < 0.7.1-0.20250129155113-4c6e03c463141; fixed in 0.7.1-0.20250129155113-4c6e03c463141

## Suggested inspection (read-only)
- Go github.com/argoproj/gitops-engine: 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/gitops-engine.
- 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-274v-mgcv-cm8j (GitHub-reviewed advisory GHSA-274v-mgcv-cm8j lists affected ranges: Go github.com/argoproj/gitops-engine >=0.7.2 =0 <0.7.1-0.20250129155113-4c6e03c463141)

Commands are suggestions: review each one before running it.