Skip to main content
VulnerabilityPublished

CVE-2025-47933: argoproj argo-cd · Cross-site Scripting

Affects argoproj argo-cdSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical · fixed in 3.0.4 : patch argoproj argo-cd as a priority.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.4, 2.14.13, 2.13.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade argoproj/argo-cd to 3.0.4, 2.14.13 or 2.13.8.

Affected software

ProductAffectedFixed in
GitHubargoproj/argo-cdpkg:github/argoproj/argo-cdOther threatsAffected
  • <2.13.8
  • >=2.13.0 <2.13.8
  • <2.14.13
  • >=2.14.0 <2.14.13
  • <3.0.4
Fixed in
  • 2.13.8
  • 2.14.13
  • 3.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should prioritize upgrading Argo CD installations to the patched versions 2.13.8, 2.14.13, or 3.0.4 immediately. Beyond patching, organizations should implement strict access controls to limit repository edit permissions only to trusted personnel, minimizing the attack surface. Employing Web Application Firewalls (WAFs) with rules to detect and block suspicious URL parameters or script injections on the Argo CD interface can provide an additional layer of defense. Regularly auditing and monitoring API usage and user activity logs for anomalous behavior can help detect exploitation attempts early. Organizations should also educate users with edit permissions about phishing risks and the dangers of clicking on untrusted links. Implementing Content Security Policy (CSP) headers in the Argo CD web interface can help mitigate the impact of XSS by restricting script execution sources. Finally, integrating vulnerability scanning and security testing into the CI/CD pipeline can help identify similar issues proactively.

Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Prior to versions 2.13.8, 2.14.13, and 3.0.4, an attacker can perform arbitrary actions on behalf of the victim via the API. 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. This issue has been patched in versions 2.13.8, 2.14.13, and 3.0.4.

References

Community reviews

Loading reviews…