CVE-2025-47933: Argo CD allows cross-site scripting on repositories page
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: github.com/argoproj/argo-cd/v2 (Go) 2.13.8, 2.14.13; github.com/argoproj/argo-cd/v3 (Go) 3.0.4; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250529T205903-1.1.
- Severity is disputed: the assigning authority (CNA) scores it 9.1, NVD 5.4.
Low priority for now. Upgrade to github.com/argoproj/argo-cd/v2 (Go) 2.13.8, 2.14.13; github.com/argoproj/argo-cd/v3 (Go) 3.0.4; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250529T205903-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 29, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 42th percentile
- CWE
- CWE-79
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.4
- CNA · GitHub_M
- 9.1
- 3.7 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| argoproj | argo cd | cpe:2.3:a:argoproj:argo_cd |
Limit the impact of XSS
This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.
Check security headersAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- argoproj argo cd1.2.1 and later · before 2.13.8
- argoproj argo cd2.14.0 and later · before 2.14.13
- argoproj argo cd3.0.0 and later · before 3.0.4
- argoproj argo cd1.2.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
argoproj argo-cd
- >= 1.2.0-rc1, <= 1.8.7, >= 2.0.0-rc3, < 2.13.8, >= 2.14.0-rc1, < 2.14.13, >= 3.0.0-rc1, < 3.0.4affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/argoproj/argo-cd | from 1.2.0-rc1 · up to and including 1.8.7 | — |
| Go | github.com/argoproj/argo-cd | from 1.2.0-rc1 | — |
| Go | github.com/argoproj/argo-cd/v2 | from 2.0.0-rc3 · before 2.13.8 | 2.13.8 |
| Go | github.com/argoproj/argo-cd/v2 | from 2.14.0-rc1 · before 2.14.13 | 2.14.13 |
| Go | github.com/argoproj/argo-cd/v3 | before 3.0.4 | 3.0.4 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20250529T205903-1.1 | 0.0.20250529T205903-1.1 |
| Red Hat:openshift_gitops:1.16::el8 | openshift-gitops-argocd-cli | before 0:1.16.1-26.el8 | 0:1.16.1-26.el8 |
| Red Hat:openshift_gitops:1.16::el8 | openshift-gitops-argocd-cli-redistributable | before 0:1.16.1-26.el8 | 0:1.16.1-26.el8 |
| Red Hat:openshift_gitops:1.16::el9 | microshift-gitops | before 0:1.16.1-10.el9 | 0:1.16.1-10.el9 |
| Red Hat:openshift_gitops:1.16::el9 | microshift-gitops-release-info | before 0:1.16.1-10.el9 | 0:1.16.1-10.el9 |
| Red Hat:openshift_gitops:1.16::el9 | openshift-gitops-argocd-cli | before 0:1.16.1-10.el9 | 0:1.16.1-10.el9 |
| Red Hat:openshift_gitops:1.16::el9 | openshift-gitops-argocd-cli-redistributable | before 0:1.16.1-10.el9 | 0:1.16.1-10.el9 |
Same product
argoproj: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-55190Argo CD: Project API Token Exposes Repository Credentials41Plan
- CVE-2022-29165Argo CD will blindly trust JWT claims if anonymous access is enabled41Plan
- CVE-2024-21652Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-41666Jul 24, 2024 · The Argo CD web terminal session does not handle the revocation of user permissions properly.26Monitor
- ← EarlierCVE-2025-23216Jan 30, 2025 · Argo CD does not scrub secret values from patch errors27Monitor
- Later →CVE-2025-55191Sep 30, 2025 · Repository Credentials Race Condition Crashes Argo CD Server21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/argoproj/argo-cd/v2 | 2.13.8 | Package registry (OSV) |
| Go:github.com/argoproj/argo-cd/v2 | 2.14.13 | Package registry (OSV) |
| Go:github.com/argoproj/argo-cd/v3 | 3.0.4 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250529T205903-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:microshift-gitops | 0:1.16.1-10.el9 · Red Hat:openshift_gitops:1.16::el9 | Package registry (OSV) |
| red hat:microshift-gitops-release-info | 0:1.16.1-10.el9 · Red Hat:openshift_gitops:1.16::el9 | Package registry (OSV) |
| red hat:openshift-gitops-argocd-cli | 0:1.16.1-26.el8 · Red Hat:openshift_gitops:1.16::el8 | Package registry (OSV) |
| red hat:openshift-gitops-argocd-cli-redistributable | 0:1.16.1-26.el8 · Red Hat:openshift_gitops:1.16::el8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-45738412 days apartArgo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation34Monitor
- CVE-2024-28175442 days apartCross-site scripting on application summary component in argo-cd21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
nvd-primary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.