CVE-2025-47933 is a critical-severity (CVSS 9) Cross-site Scripting (XSS) vulnerability in github.com/argoproj/argo-cd. A fix is available for github.com/argoproj/argo-cd — see the affected versions and patch details below.
Argo CD allows cross-site scripting on repositories page
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-47933.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-47933 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 383,485 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/argoproj/argo-cd🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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. Due to the improper filtering of URL protocols in the repository page, an attacker can achieve cross-site scripting with permission to edit the repository.
In ui/src/app/shared/components/urls.ts, the following code exists to parse the repository URL.
Since this code doesn't validate the protocol of repository URLs, it's possible to inject javascript: URLs here.
As the return value of this function is used in the href attribute of the a tag, it's possible to achieve cross-site scripting by using javascript: URLs.
Browsers may return the proper hostname for javascript: URLs, allowing exploitation of this vulnerability.
Patches
A patch for this vulnerability has been released in the following Argo CD versions:
- v3.0.4
- v2.14.13
- v2.13.8
The patch incorporates a way to validate the URL being passed in. Returning null if the validation fails.
Workarounds
There are no workarounds other than depending on the browser to filter the URL.
Credits
Disclosed by @Ry0taK RyotaK.
For more information
Open an issue in the Argo CD issue tracker or discussions Join us on Slack in channel #argo-cd
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/argoproj/argo-cd | ≥ 1.2.0-rc1 | No fix |
| 🐹Go | github.com/argoproj/argo-cd/v2 | ≥ 2.0.0-rc3&&< 2.13.8 | 2.13.8go get github.com/argoproj/argo-cd/v2@v2.13.8 |
| 🐹Go | github.com/argoproj/argo-cd/v2 | ≥ 2.14.0-rc1&&< 2.14.13 | 2.14.13go get github.com/argoproj/argo-cd/v2@v2.14.13 |
| 🐹Go | github.com/argoproj/argo-cd/v3 | all versions | 3.0.4go get github.com/argoproj/argo-cd/v3@v3.0.4 |
Affected Products
argo cdargoprojDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-cd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of github.com/argoproj/argo-cd has shipped for CVE-2025-47933 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift GitOps 1.14 | openshift-gitops-1/argocd-rhel8:v1.14.4-1 | RHSA-2025:8274 |
| Red Hat OpenShift GitOps 1.15 | openshift-gitops-1/argocd-extensions-rhel8:v1.15.3-3 | RHSA-2025:8277 |
| Red Hat OpenShift GitOps 1.16 | microshift-gitops-0:1.16.1-10.el9 | RHSA-2025:8269 |
| Red Hat OpenShift GitOps 1.16 | openshift-gitops-1/argocd-extensions-rhel8:v1.16.1-4 | RHSA-2025:8278 |
Frequently Asked Questions
Is CVE-2025-47933 in your dependencies?
Find it across Go, including transitive dependencies.