Cross-Site Scripting (XSS) in github.com/argoproj/argo-cd/v3 (CVE-2026-45738)
Summary
Cross-site scripting in github.com/argoproj/argo-cd/v3 (CVE-2026-45738). Confidential information can be exposed externally. Mitigation: upgrade to 3.2.12, 3.3.10, 3.4.2 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45738 has been found in github.com/argoproj/argo-cd/v3.
Confidential information can be exposed externally. CVSS score: 7.3/10.
What to do: upgrade github.com/argoproj/argo-cd/v3 to 3.2.12, 3.3.10, 3.4.2 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-cd/v3 CVE-2026-45738" on the vendor's site.
CVE-2026-45738 (github.com/argoproj/argo-cd/v3) — CWE-79 / CVSS v3 7.3
Attack vector: remote (network-reachable)
Patched: 3.2.12, 3.3.10, 3.4.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in github.com/argoproj/argo-cd/v3.
Check the vendor advisory for the affected versions of github.com/argoproj/argo-cd/v3.
Severity: High (CVSS 7.3/10). Confidential information can be exposed externally.
Update to 3.2.12, 3.3.10, 3.4.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/argoproj/argo-cd/v3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/argoproj/argo-cd/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/argoproj/argo-cd/v3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/argoproj/argo-cd/v3 to 3.2.12, 3.3.10, 3.4.2ステージング環境で 3.2.12, 3.3.10, 3.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov