| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| In JetBrains TeamCity before 2026.2.1 arbitrary file read was possible via symlinks in Mercurial subrepositories |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Create Project dialog was possible |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 the TFS helper server was exposed on all network interfaces |
| In JetBrains Junie CLI before 26.6.29 sensitive environment variables were exposed in session event logs |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via build attribute injection |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 improper authorization allowed viewing build process details via agent stacktraces |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS on the Disk Usage and Build Time pages was possible |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 DoS via agent command results was possible |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Shared Resources build feature was possible |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in the external artifact cache |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 missing authorization in the Kubernetes integration allowed project viewers to use stored credentials |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 XXE in the .NET build steps auto-discovery was possible |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Promote build dialog was possible |
| In JetBrains TeamCity before 2026.1.3 privilege escalation was possible by issuing new tokens from a restricted access token |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via best-fit character mapping in Perforce settings |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Perforce settings |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Mercurial VCS root settings |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in project import archives |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in the pipeline YAML file path |
| In JetBrains TeamCity before 2026.1.3, 2025.11.8 disclosure of password parameter values to project viewers was possible |