CVE-2025-52879: JetBrains TeamCity · Cross-site Scripting
Affects JetBrains TeamCitySource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium : upgrade to 2025.03.3 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2025.03.3
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 org.jetbrains.teamcity/teamcity-server to 2025.03.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.jetbrains.teamcity/teamcity-serverpkg:maven/org.jetbrains.teamcity/teamcity-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediate upgrade to JetBrains TeamCity version 2025.03.3 or later once available, as this version addresses the reflected XSS vulnerability in the NPM Registry integration.
- Until patching is possible, restrict access to the TeamCity web interface to trusted networks and users, minimizing exposure to potential attackers.
- Implement strict Content Security Policy (CSP) headers on the TeamCity server to limit the execution of unauthorized scripts and reduce the impact of XSS attacks.
- Conduct user awareness training focused on phishing and social engineering risks, as user interaction is required for exploitation.
- Review and harden user privileges within TeamCity, ensuring that only necessary users have high-level permissions to reduce the pool of potential attackers.
- Monitor TeamCity logs and web traffic for unusual or suspicious requests that may indicate attempted exploitation of the reflected XSS vulnerability.
- Employ web application firewalls (WAFs) with rules targeting reflected XSS patterns, specifically tuned for TeamCity’s NPM Registry integration endpoints.
- Consider isolating CI/CD environments and enforcing network segmentation to limit lateral movement if an attacker exploits this vulnerability.
Description
In JetBrains TeamCity before 2025.03.3 reflected XSS in the NPM Registry integration was possible