Cross-site scripting on application summary component
CVE-2024-28175GHSA-jwv5-8mqv-g387
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.9.0, < 2.9.8>= 2.10.0, < 2.10.3>= 2.0.0, < 2.8.12
- Fixed in
- 2.10.3, 2.9.8, 2.8.12
Go github.com/argoproj/argo-cd
- Affected
- >= 1.0.0, <= 1.8.7
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jwv5-8mqv-g387 lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.9.0 =2.10.0 =2.0.0 =1.0.0 <=1.8.7
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-2024-28175: 0.65% estimated exploitation activity in the next 30 days; percentile 51.40 (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.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-jwv5-8mqv-g387
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-2024-28175 Advisory: Cross-site scripting on application summary component IDs: CVE-2024-28175, GHSA-jwv5-8mqv-g387 Record: https://patchnext.com/advisories/cve-2024-28175 (revision 1, source checked 26 Oct 2026, 15:04 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.10.3, 2.9.8, 2.8.12. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/argoproj/argo-cd/v2: affected >= 2.9.0, < 2.9.8; >= 2.10.0, < 2.10.3; >= 2.0.0, < 2.8.12; fixed in 2.10.3, 2.9.8, 2.8.12 - Go github.com/argoproj/argo-cd: affected >= 1.0.0, <= 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: 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. - 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-jwv5-8mqv-g387 (GitHub-reviewed advisory GHSA-jwv5-8mqv-g387 lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.9.0 =2.10.0 =2.0.0 =1.0.0 <=1.8.7) Commands are suggestions: review each one before running it.
Loading voting…