Argo CD allows cross-site scripting on repositories page
CVE-2025-47933GHSA-2hj5-g64g-fp6p
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/argoproj/argo-cd/v2
- Affected
- >= 2.0.0-rc3, < 2.13.8>= 2.14.0-rc1, < 2.14.13
- Fixed in
- 2.13.8, 2.14.13
Go github.com/argoproj/argo-cd/v3
- Affected
- < 3.0.4
- Fixed in
- 3.0.4
Go github.com/argoproj/argo-cd
- Affected
- >= 1.2.0-rc1, <= 1.8.7
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2hj5-g64g-fp6p lists affected ranges: Go github.com/argoproj/argo-cd >=1.2.0-rc1 =2.0.0-rc3 =2.14.0-rc1 =0 <3.0.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.0 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
- EPSS
- CVE-2025-47933: 0.49% estimated exploitation activity in the next 30 days; percentile 41.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-2hj5-g64g-fp6p
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-47933 Advisory: Argo CD allows cross-site scripting on repositories page IDs: CVE-2025-47933, GHSA-2hj5-g64g-fp6p Record: https://patchnext.com/advisories/cve-2025-47933 (revision 1, source checked 26 Oct 2026, 15:09 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.0) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-cd/v2 2.14.13, 2.13.8; github.com/argoproj/argo-cd/v3 3.0.4. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/argoproj/argo-cd/v2: affected >= 2.0.0-rc3, < 2.13.8; >= 2.14.0-rc1, < 2.14.13; fixed in 2.13.8, 2.14.13 - Go github.com/argoproj/argo-cd/v3: affected < 3.0.4; fixed in 3.0.4 - Go github.com/argoproj/argo-cd: affected >= 1.2.0-rc1, <= 1.8.7 ## Suggested inspection (read-only) - Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager. - Go github.com/argoproj/argo-cd/v3: check the installed version with your package manager. - Go github.com/argoproj/argo-cd: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd/v3, github.com/argoproj/argo-cd. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-2hj5-g64g-fp6p (GitHub-reviewed advisory GHSA-2hj5-g64g-fp6p lists affected ranges: Go github.com/argoproj/argo-cd >=1.2.0-rc1 =2.0.0-rc3 =2.14.0-rc1 =0 <3.0.4) Commands are suggestions: review each one before running it.
Loading voting…