dbcve.org
Argo CdApplication · Argoproj

CVE-2026-45738

HIGH · 8.7 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 →
91/100
Remediation priority · Urgent
Remotely reachable 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. Prior to 3.2.12, 3.3.10, and 3.4.2, Argo CD users with application write access can set link.argocd.argoproj.io/* annotations whose pipe-separated values are rendered by ui/src/app/applications/components/application-summary/application-summary.tsx in the Summary tab URLs section as anchor href values without URL validation, allowing javascript: execution in a higher-privileged user's authenticated Argo CD origin session. 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

A stored Cross-Site Scripting (XSS) vulnerability in Argo CD allows users with application write access to inject malicious javascript: URLs via link.argocd.argoproj.io/* annotations. These pipe-separated values are rendered in the application Summary tab's URL section as anchor href attributes without proper URL validation, enabling script execution in higher-privileged users' authenticated sessions.

MitigationUpgrade to Argo CD versions 3.2.12, 3.3.10, or 3.4.2 which implement URL validation on the rendered annotations to block javascript: and other dangerous URL schemes.

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.12>= 3.3.0, < 3.3.10>= 3.4.0, < 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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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. Identify Argo CD version
    Run 'argocd version' or check the Argo CD deployment/deployment.yaml for the image version tag
    Affected if The installed version is < 3.2.12, OR >= 3.3.0 AND < 3.3.10, OR >= 3.4.0 AND < 3.4.2
  2. List Applications with link annotations
    Run 'kubectl get applications -o json' and filter for annotations matching 'link.argocd.argoproj.io/*'
    Affected if Any Application resource contains annotations with the 'link.argocd.argoproj.io/' prefix
  3. Inspect annotation values for dangerous schemes
    Examine the values of link.argocd.argoproj.io/* annotations. Look for 'javascript:' or other non-http(s) URL schemes in the pipe-separated values
    Affected if The annotation values contain 'javascript:' URLs or other potentially dangerous URL schemes (e.g., data:, vbscript:)

You are affected if your Argo CD version falls within the vulnerable ranges AND Applications exist with link.argocd.argoproj.io/* annotations containing javascript: or other dangerous URL schemes.

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 to Argo CD versions 3.2.12, 3.3.10, or 3.4.2 which implement URL validation on the rendered annotations to block javascript: and other dangerous URL schemes.

Recommended fix High confidence

3.2.12, 3.3.10, or 3.4.2

  1. 1. Identify the current Argo CD version running in your Kubernetes cluster using: kubectl get deployment argocd-server -n argocd -o jsonpath='{.spec.template.spec.containers[0].image}'
  2. 2. Based on your current version, upgrade to one of the fixed releases: 3.2.12, 3.3.10, or 3.4.2
  3. 3. If running Argo CD via Helm: helm repo update && helm upgrade argocd argo/argo-cd --version <fixed-version> -n argocd
  4. 4. If using Kubernetes manifests: kubectl set image deployment/argocd-server argocd-server=argoproj/argo-cd:<fixed-version> -n argocd
  5. 5. Wait for the rollout to complete: kubectl rollout status deployment/argocd-server -n argocd
  6. 6. Verify the upgraded version: kubectl get deployment argocd-server -n argocd -o jsonpath='{.spec.template.spec.containers[0].image}'
Caveat Review Argo CD release notes for breaking changes between your current version and target fixed version before upgrading

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

Fix this in Argo Cd Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45738 — 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-45738 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