dbcve.org
Argo CdApplication · Argoproj

CVE-2026-45737

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 3.2.12 / 3.3.10 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In affected versions of Argo CD (3.2.0-3.2.11, 3.3.0-3.3.9, 3.4.0-3.4.1), the ServerSideDiff feature exposes Kubernetes Secret values embedded in the kubectl.kubernetes.io/last-applied-configuration annotation. The HideSecretData function fails to fully sanitize ResourceDiff.TargetState and LiveState for predicted live Secret objects, causing sensitive data, stringData, and annotations to appear in UI or CLI diffs.

MitigationUpgrade Argo CD to version 3.2.12, 3.3.10, or 3.4.2 or later. After upgrading, verify that Secret values are no longer exposed in diff outputs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Argo CdApplication
Affected:>= 3.2.0, < 3.2.12>= 3.3.9, < 3.3.10>= 3.4.1, < 3.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Argo CD version
    Run 'argocd version' to retrieve the CLI and server versions, or check the Argo CD deployment/deployment.yaml for the image version tag
    Affected if The version is 3.2.0-3.2.11, 3.3.0-3.3.9, or 3.4.0-3.4.1
  2. Verify ServerSideDiff feature is enabled
    Check the Argo CD configmap (argocd-cm) or your Application spec for 'serverSideDiff' in the resource.customizations or review whether the feature flag is set
    Affected if ServerSideDiff is enabled in the Argo CD installation
  3. Inspect a Secret resource diff output
    Apply a Kubernetes Secret to the cluster, then run 'argocd app diff <app-name>' or view the diff in the Argo CD UI for an Application containing that Secret
    Affected if The diff output displays the Secret's 'data', 'stringData', or 'metadata.annotations' fields (including the kubectl.kubernetes.io/last-applied-configuration annotation) with actual values instead of redacted placeholder text

A user is affected if they run a vulnerable Argo CD version (3.2.0-3.2.11, 3.3.0-3.3.9, or 3.4.0-3.4.1) with ServerSideDiff enabled and observe unredacted Secret values in diff outputs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2.12 / 3.3.10 / 3.4.2 or later
Fixed in 3.2.123.3.103.4.2
Interim mitigation

Upgrade Argo CD to version 3.2.12, 3.3.10, or 3.4.2 or later. After upgrading, verify that Secret values are no longer exposed in diff outputs.

Recommended fix High confidence

Upgrade to Argo CD 3.2.12, 3.3.10, or 3.4.2 (preferably 3.4.2 for latest features and fixes)

  1. Identify your current Argo CD version using `argocd version` or checking your deployment
  2. Determine which release line you're on (3.2.x, 3.3.x, or 3.4.x)
  3. Upgrade to the appropriate fixed version: 3.2.12, 3.3.10, or 3.4.2
  4. For Kubernetes deployments, update the Argo CD image in your manifests or Helm chart: `image: argoproj/argo-cd:v3.4.2` (or your chosen fixed version)
  5. Apply the upgrade: `kubectl apply -f your-argo-cd-manifests.yaml`
  6. Verify the upgrade completed successfully: `argocd version`
  7. Test the ServerSideDiff functionality with a Secret resource to confirm sensitive data is now properly hidden in diffs

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Argo Cd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45737 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45737 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data