Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.3

Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation

CVE-2026-45738GHSA-h98r-wv3h-fr38

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.

Add to your agent

Affected packages

  • Go github.com/argoproj/argo-cd/v2

    Affected
    <= 2.14.21
    Fixed in
    no fixed version recorded

  • Go github.com/argoproj/argo-cd/v3

    Affected
    < 3.2.12>= 3.3.0-rc1, <= 3.3.9>= 3.4.0-rc1, <= 3.4.1
    Fixed in
    3.3.10, 3.4.2, 3.2.12

  • Go github.com/argoproj/argo-cd

    Affected
    <= 1.8.7
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-45738: 0.61% estimated exploitation activity in the next 30 days; percentile 49.06 (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 A user with application write access (developer role) can set link.argocd.argoproj.io/ annotations on any ArgoCD Application. These annotation values are rendered in the Summary tab's URLs section as <a href elements without URL validation. Using the pipe-separator trick (Display Text | javascript:...), an attacker can inject a javascript: URI while displaying a legitimate-looking label (e.g. GitHub Repo). When a higher-privileged user (admin) clicks the link, arbitrary JavaScript executes in the ArgoCD origin context in the admin's authenticated session context, enabling API exfiltration and privilege escalation from developer to admin. Details Vulnerable sink: ui/src/app/applications/components/application-summary/application-summary.tsx:277 The annotation value is split on |. parts[0] becomes the visible link label; parts[1] becomes the href. No call to isValidURL() is made, unlike the protected ApplicationURLs component (application-urls.tsx:72,80) which does validate…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-h98r-wv3h-fr38

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-2026-45738

Advisory: Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation
IDs: CVE-2026-45738, GHSA-h98r-wv3h-fr38
Record: https://patchnext.com/advisories/cve-2026-45738 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
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/v3 3.4.2, 3.3.10, 3.2.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected <= 2.14.21
- Go github.com/argoproj/argo-cd/v3: affected < 3.2.12; >= 3.3.0-rc1, <= 3.3.9; >= 3.4.0-rc1, <= 3.4.1; fixed in 3.3.10, 3.4.2, 3.2.12
- Go github.com/argoproj/argo-cd: affected <= 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-h98r-wv3h-fr38 (GitHub-reviewed advisory GHSA-h98r-wv3h-fr38 lists affected ranges: Go github.com/argoproj/argo-cd/v3 >=0 =3.3.0-rc1 =3.4.0-rc1 =0 =0 <=1.8.7)

Commands are suggestions: review each one before running it.

Loading voting…