Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-45737: 0.52% estimated exploitation activity in the next 30 days; percentile 44.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The original fix for GHSA-3v3m-wc6v-x4x3 is incomplete. argocd app diff --server-side-diff can still expose Kubernetes Secret values embedded in the kubectl.kubernetes.io/last-applied-configuration annotation. The prior fix masks top-level Secret data in ServerSideDiff responses, but it does not fully sanitize Secret data stored inside the last-applied-configuration annotation. If a Secret was previously created or updated using client-side apply, that annotation may contain raw data, stringData, and sensitive annotations. These values can be shown in UI/CLI diffs. Details The ServerSideDiff endpoint returns ResourceDiff.TargetState / LiveState based on server-side dry-run output. Kubernetes server-side dry-run can return a full predicted live Secret object that carries forward existing live annotations, including: kubectl.kubernetes.io/last-applied-configuration For Secrets created with client-side apply, that annotation can contain a JSON-serialized Secret manifest with…

Published by the source

19 May 2026, 15:54 UTC

Last modified by the source

19 May 2026, 15:54 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rg3g-4rw9-gqrp

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

# Patch Next advisory brief: CVE-2026-45737

Advisory: Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations
IDs: CVE-2026-45737, GHSA-rg3g-4rw9-gqrp
Record: https://patchnext.com/advisories/cve-2026-45737 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/argoproj/argo-cd/v3 3.4.2, 3.3.10, 3.2.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v3: affected >= 3.2.0, <= 3.2.11; >= 3.3.0-rc1, <= 3.3.9; >= 3.4.0-rc1, <= 3.4.1; fixed in 3.3.10, 3.4.2, 3.2.12

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v3: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v3.
- 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-rg3g-4rw9-gqrp (GitHub-reviewed advisory GHSA-rg3g-4rw9-gqrp lists affected ranges: Go github.com/argoproj/argo-cd/v3 >=3.2.0 =3.3.0-rc1 =3.4.0-rc1 <=3.4.1)

Commands are suggestions: review each one before running it.