argoproj · Argo CD · published 2026-07-15
CVE-2026-45738Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-45738 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 49% of all CVEs. This Argo CD vulnerability: CVSS 7.3 (v3.1), a successful attack gives total control of the component. Fixed upstream in Argo CD 3.4.2, 3.3.10, 3.2.12. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Argo CD 3.4.2, 3.3.10, 3.2.12.
Patch events
OrchestrationArgo CD
Argo CD security releases: 3.4.2, 3.3.10, 3.2.12
Upgrade to
3.4.23.3.103.2.12Why: CVE-2026-45738: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.6% (50th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.3 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- argoproj argo-cd
< 3.2.12(affected)>= 3.3.0, < 3.3.10(affected)>= 3.4.0-rc1, < 3.4.2(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.