CVE-2025-67741: JetBrains TeamCity · Cross-site Scripting
Affects JetBrains TeamCitySource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium · fixed in 2025.11 : update JetBrains TeamCity when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- 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 2025.11
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Dec 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JetBrains TeamCity | Affected
| Fixed in– |
AI-suggested
1. Apply the official JetBrains TeamCity update to version 2025.11 or later as soon as it becomes available to remediate the vulnerability. 2. Until patching is possible, implement strict input validation and sanitization on all user-controllable inputs, especially session attributes, to prevent injection of malicious scripts. 3. Enforce Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts within the TeamCity web interface. 4. Limit user privileges within TeamCity to the minimum necessary, reducing the attack surface for privilege-limited attackers. 5. Monitor TeamCity logs for unusual activity or attempts to inject scripts. 6. Educate users to be cautious with links and interactions within the TeamCity environment to reduce the risk of user interaction exploitation. 7. Consider network segmentation and access controls to restrict exposure of TeamCity interfaces to trusted users only.
Description
In JetBrains TeamCity before 2025.11 stored XSS was possible via session attribute