CVE-2026-45737

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

Published Jul 15, 2026 CVSS 3.1 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 3.2.0 until 3.2.12, 3.3.10, and 3.4.2, Argo CD ServerSideDiff can expose Kubernetes Secret values embedded in the kubectl.kubernetes.io/last-applied-configuration annotation because HideSecretData(target, live, ...) does not fully sanitize ResourceDiff.TargetState and LiveState predicted live Secret objects, allowing sensitive data, stringData, and annotations to appear in UI or CLI diffs. This issue is fixed in versions 3.2.12, 3.3.10, and 3.4.2.

Analysis

AI-generated

Technical impact

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 3.2.0 until 3.2.12, 3.3.10, and 3.4.2, Argo CD ServerSideDiff can expose Kubernetes Secret values embedded in the kubectl.kubernetes.io/last-applied-configuration annotation because HideSecretData(target, live, ...) does not fully sanitize ResourceDiff.TargetState and LiveState predicted live Secret objects, allowing sensitive data, stringData, and annotations to appear in UI or CLI diffs. This issue is fixed in versions 3.2.12, 3.3.10, and 3.4.2.

Affected Systems

The vulnerability affects argoproj:argo-cd, specifically Argo CD versions from 3.2.0 up to but not including 3.2.12, 3.3.10, and 3.4.2. Versions 3.2.12, 3.3.10, and 3.4.2 contain the fix and are not vulnerable.

Risk and Exploitability

The CVSS score of 6.3 indicates a moderate severity. The EPSS score of <1% suggests low likelihood of exploitation at the time of analysis. The vulnerability is not listed in the CISA KEV catalog. Attackers would need authenticated access to the Argo CD server and the ability to trigger ServerSideDiff, typically via the web UI or CLI, which is why the attack vector is inferred to be remote. If the server is publicly exposed or RBAC misconfigured, the risk of exposure increases.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Argo CD to version 3.2.12, 3.3.10, 3.4.2 or later to apply the vendor patch.
  • Restrict external access to the Argo CD web UI and CLI to trusted users, and enforce least‑privilege RBAC rules so that only authorized personnel can request ServerSideDiff operations.
  • Review and cleanse any kubectl.kubernetes.io/last-applied-configuration annotations on Secret objects before applying or displaying them, and monitor for unauthorized diff requests in logs.

Generated by OpenCVE AI on July 31, 2026 at 02:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-rg3g-4rw9-gqrp Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Argoproj
Argoproj argo-cd
Vendors & Products Argoproj
Argoproj argo-cd
Type Values Removed Values Added
Description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 3.2.0 until 3.2.12, 3.3.10, and 3.4.2, Argo CD ServerSideDiff can expose Kubernetes Secret values embedded in the kubectl.kubernetes.io/last-applied-configuration annotation because HideSecretData(target, live, ...) does not fully sanitize ResourceDiff.TargetState and LiveState predicted live Secret objects, allowing sensitive data, stringData, and annotations to appear in UI or CLI diffs. This issue is fixed in versions 3.2.12, 3.3.10, and 3.4.2.
Title Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations
Weaknesses CWE-200
CWE-212
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-212

    Improper Removal of Sensitive Information Before Storage or Transfer

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 16, 2026, 7:14 PM
Reserved
May 13, 2026, 6:54 AM
Status
Analyzed
Published
Jul 15, 2026, 8:17 PM
Modified
Oct 24, 2026, 9:10 PM