CVE-2025-47933

CVE-2025-47933 is a critical-severity cross-site scripting (XSS) vulnerability in github.com/argoproj/argo-cd (go), affecting versions >= 1.2.0-rc1, <= 1.8.7. It is fixed in 2.13.8, 2.14.13, 3.0.4.

Summary

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

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.

https://github.com/argoproj/argo-cd/blob/0ae5882d5ae9fe88efc51f65ca8543fb8c3a0aa1/ui/src/app/shared/components/urls.ts#L14-L26

Since this code doesn't validate the protocol of repository URLs, it's possible to inject javascript: URLs here.

https://github.com/argoproj/argo-cd/blob/0ae5882d5ae9fe88efc51f65ca8543fb8c3a0aa1/ui/src/app/shared/components/repo.tsx#L5-L7

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-47933 has a CVSS score of 9.0 (Critical). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.13.8, 2.14.13, 3.0.4); upgrading removes the vulnerable code path.

Affected versions

github.com/argoproj/argo-cd (>= 1.2.0-rc1, <= 1.8.7) github.com/argoproj/argo-cd/v2 (>= 2.0.0-rc3, < 2.13.8) github.com/argoproj/argo-cd/v2 (>= 2.14.0-rc1, < 2.14.13) github.com/argoproj/argo-cd/v3 (< 3.0.4)

Security releases

github.com/argoproj/argo-cd/v2 → 2.13.8 (go) github.com/argoproj/argo-cd/v2 → 2.14.13 (go) github.com/argoproj/argo-cd/v3 → 3.0.4 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

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.

Frequently Asked Questions

  1. What is CVE-2025-47933? CVE-2025-47933 is a critical-severity cross-site scripting (XSS) vulnerability in github.com/argoproj/argo-cd (go), affecting versions >= 1.2.0-rc1, <= 1.8.7. It is fixed in 2.13.8, 2.14.13, 3.0.4. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
  2. How severe is CVE-2025-47933? CVE-2025-47933 has a CVSS score of 9.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2025-47933?
    • github.com/argoproj/argo-cd (go) (versions >= 1.2.0-rc1, <= 1.8.7)
    • github.com/argoproj/argo-cd/v2 (go) (versions >= 2.0.0-rc3, < 2.13.8)
    • github.com/argoproj/argo-cd/v3 (go) (versions < 3.0.4)
  4. Is there a fix for CVE-2025-47933? Yes. CVE-2025-47933 is fixed in 2.13.8, 2.14.13, 3.0.4. Upgrade to this version or later.
  5. Is CVE-2025-47933 exploitable, and should I be worried? Whether CVE-2025-47933 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2025-47933 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2025-47933?
    • Upgrade github.com/argoproj/argo-cd/v2 to 2.13.8 or later
    • Upgrade github.com/argoproj/argo-cd/v2 to 2.14.13 or later
    • Upgrade github.com/argoproj/argo-cd/v3 to 3.0.4 or later

Other vulnerabilities in github.com/argoproj/argo-cd

CVE-2026-45738CVE-2025-59531CVE-2025-47933CVE-2025-23216CVE-2024-40634

Stop the waste.
Protect your environment with Kodem.