CVE-2024-28175: Cross-site scripting on application summary component
Summary Due to the improper URL protocols filtering of links specified in the link.argocd.argoproj.io annotations in the application summary component, an attacker can achieve cross-site scripting with elevated permissions. Impact All unpatched versions of Argo CD starting with v1.0.0 are vulnerable to a cross-site scripting (XSS) bug allowing a malicious user to inject a javascript: link in the UI.
Published Mar 15, 2024 · Updated May 20, 2024
Affected packages
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.9.0, < 2.9.8
- Fixed in
- 2.9.8
- Check
go list -m github.com/argoproj/argo-cd/v2
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.10.0, < 2.10.3
- Fixed in
- 2.10.3
- Check
go list -m github.com/argoproj/argo-cd/v2
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.0.0, < 2.8.12
- Fixed in
- 2.8.12
- Check
go list -m github.com/argoproj/argo-cd/v2
github.com/argoproj/argo-cd
- Ecosystem
- Go
- Affected
- >= 1.0.0, <= 1.8.7
- Fixed in
- No patched version yet
- Check
go list -m github.com/argoproj/argo-cd
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Due to the improper URL protocols filtering of links specified in the link.argocd.argoproj.io annotations in the application summary component, an attacker can achieve cross-site scripting with elevated permissions.
Impact
All unpatched versions of Argo CD starting with v1.0.0 are vulnerable to a cross-site scripting (XSS) bug allowing a malicious user to inject a javascript: link in the UI. When clicked by a victim user, the script will execute with the victim's permissions (up to and including admin).
This vulnerability allows an attacker to perform arbitrary actions on behalf of the victim via the API, such as creating, modifying, and deleting Kubernetes resources.
Patches
A patch for this vulnerability has been released in the following Argo CD versions:
- v2.10.3
- v2.9.8
- v2.8.12
Workarounds
There are no completely-safe workarounds besides upgrading. The safest alternative, if upgrading is not possible, would be to create a Kubernetes admission controller to reject any resources with an annotation starting with link.argocd.argoproj.io or reject the resource if the value use an improper URL protocol. This validation will need to be applied in all clusters managed by ArgoCD.
Mitigations
- Avoid clicking external links presented in the UI.
The link's title is user-configurable. So even if you hover the link, and the tooltip looks safe, the link might be malicious. The only way to be certain that the link is safe is to inspect the page's source.
- Carefully limit who has permissions to edit Kubernetes resource manifests (this is configured in RBAC for ArgoCD).
The external-links are set as annotations on Kubernetes resources. Any persona with write access to resources managed by ArgoCD could be an actor.
References
Documentation for the external links feature
Credits
Disclosed by RyotaK (@Ry0taK)
For more information
- Open an issue in the Argo CD issue tracker or discussions
- Join us on Slack in channel #argo-cd
Credited to Ry0taK, agaudreault, crenshaw-dev.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-77459
Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
critical9.9No fixOct 15, 2026CVE-2025-55190
Argo CD's Project API Token Exposes Repository Credentials
critical9.9Sep 4, 2025CVE-2025-47933
Argo CD allows cross-site scripting on repositories page
critical9.0No fixMay 28, 2025CVE-2024-31989
ArgoCD Vulnerable to Use of Risky or Missing Cryptographic Algorithms in Redis Cache
critical9.0No fixMay 21, 2024CVE-2024-21652
Bypassing Brute Force Protection via Application Crash and In-Memory Data Loss
critical9.8Mar 18, 2024
