Summary
Ein Angreifer kann mehrere Schwachstellen in JetBrains TeamCity ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Daten zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.
Product
TeamCity ist ein Continuous Integration und Deployment Tool für Entwickler und DevOps Ingenieure.
Vulnerabilities 181
-
Critical 9.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via external pull requests
-
High 8.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via native code loading in …
-
High 8.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial repository co…
-
High 8.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via a file write bypass in …
-
High 8.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via boot classpath libraries in the …
-
High 8.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via script definitions in the Kotlin…
-
High 8.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a UI patches callback in the Kot…
-
High 8.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a context parameters callback in…
-
High 8.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 privilege escalation was possible via username handling in token authen…
-
High 8.8
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven repository settings
-
High 8.8
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a URL stream handler in the Kotl…
-
High 8.8
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a time zone callback in the Kotl…
-
High 8.8
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git submodule URLs
-
High 8.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the P4 Code Review build tab was possible
-
High 8.1
In JetBrains TeamCity before 2026.2 privilege escalation was possible via the authorization flow
-
High 8.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 missing authorization allowed any authenticated user to start …
-
High 8.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 missing authorization allowed project viewers to remove VCS ro…
-
High 8.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 project viewers could redirect GitHub App connection credentia…
-
High 8.1
In JetBrains TeamCity before 2026.2.2, 2026.1.6 the TFS helper process exposed an unauthenticated command server
-
High 8.1
In JetBrains TeamCity before 2026.2.2, 2026.1.6 a CSRF attack was possible on the Hub integration settings
-
High 8.0
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Issue Log tab was possible
-
High 8.0
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Git VCS root settings
-
High 8.0
In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in Server Health reports was possible
-
High 8.0
In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Users page was possible
-
High 7.7
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an SSRF via pipeline repository branch listing was possible
-
High 7.7
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an SSRF in AWS connection settings could expose server credent…
-
High 7.7
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 improper authorization allowed access to credentials of other …
-
High 7.7
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 improper authorization allowed publishing packages to NuGet fe…
-
High 7.7
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 access keys of parent project AWS connections could be disclos…
-
High 7.7
In JetBrains TeamCity before 2026.2.1 missing authorization allowed project viewers to download project settings
-
High 7.7
In JetBrains TeamCity before 2026.2.2, 2026.1.6 vCS root credentials could be exposed via change viewer links
-
High 7.7
In JetBrains TeamCity before 2026.2.2 missing authorization allowed project developers to read arbitrary HashiCorp Vaul…
-
High 7.6
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the NPM Registry build feature was possible
-
High 7.6
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the AWS Credentials build feature was possible
-
High 7.6
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on build and queue pages was possible
-
High 7.6
In JetBrains TeamCity before 2026.2.2, 2026.1.6 an XXE was possible in the TFS helper process
-
High 7.5
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Subversion VCS root set…
-
High 7.5
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 secure parameter values were disclosed to project viewers in p…
-
High 7.5
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial VCS root sett…
-
High 7.5
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 unauthenticated DoS via the agent protocol was possible
-
High 7.5
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via build access codes disc…
-
High 7.5
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Mercurial subrepository paths
-
High 7.5
In JetBrains TeamCity before 2026.2.1 remote code execution was possible via the Notification Rules form
-
High 7.5
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via personal builds with versioned s…
-
High 7.5
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via local repository URLs in Subvers…
-
High 7.5
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git VCS root URLs
-
High 7.5
In JetBrains TeamCity before 2026.2.2, 2026.1.6 a DoS attack was possible via unauthenticated multipart requests
-
High 7.4
In JetBrains TeamCity before 2026.1.5 untrusted build approval for GitHub fork pull requests could be bypassed
-
High 7.4
In JetBrains TeamCity before 2026.2.2, 2026.1.6 agent Push authorization keys were predictable
-
High 7.2
In JetBrains TeamCity before 2026.2, 2026.1.4 remote code execution was possible via Kubernetes Executor settings
-
High 7.2
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 arbitrary file write on the server was possible via Kotlin DSL…
-
High 7.2
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via class injection in the …
-
High 7.2
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via public reflection in the Kotlin …
-
High 7.2
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Kotlin DSL compiler arguments
-
High 7.2
In JetBrains TeamCity before 2026.2.1, 2026.1.5 code injection in generated Kotlin DSL was possible via matrix build pa…
-
High 7.2
In JetBrains TeamCity before 2026.2.2, 2026.1.6 privilege escalation to system administrator was possible via Project I…
-
High 7.2
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the…
-
High 7.2
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven dependencies of Kotlin DSL…
-
High 7.2
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via FreeMarker notification templates
-
High 7.2
In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed overwriting versioned settings of other …
-
High 7.2
In JetBrains TeamCity before 2026.2.2, 2026.1.6 code injection in parent project Kotlin DSL was possible via subproject…
-
High 7.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an LDAP injection allowed bypassing login restrictions
-
High 7.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 arbitrary file deletion on the server was possible via the Kot…
-
High 7.1
In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed queuing builds with personal changes of …
-
Medium 6.8
In JetBrains TeamCity before 2026.2 two-factor authentication bypass was possible via access token management
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Maven settings health report was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the configuration health popup was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the build Issues tab was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the Xcode runner configuration selection was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Finish Build Trigger editor was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger dependency settings was pos…
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.5 stored XSS on the external Kotlin DSL editor status page was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Promote build dialog for dependent builds wa…
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in issue tracker links was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Inspections (IntelliJ IDEA) build step edito…
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Agent Statistics tooltip was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in agent requirements was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules editor was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger branch filter settings was …
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the build Report Tab dialog was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Report Tabs settings page was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS in Maven Build Info module links was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS on the change Files tab was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS in the Issue Trackers health report was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the GitHub App repository selector was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS in the Maven Build Info project header was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for Space connections was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS in the Amazon EC2 cloud profile editor was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS in VMware vSphere cloud profile settings was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS in recipe export errors was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the thread dump page was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for VCS roots was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored and reflected XSS in Space project connection dialogs was possib…
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the JaCoCo coverage settings was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 a DOM-based XSS in the plugin installation dialog was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Create Project dialog was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.2 stored XSS in GitHub issue tracker suggestions was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.2, 2026.1.6 command injection in Project Import artifact copy scripts was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in the enforced settings restriction tooltip was possible
-
Medium 6.8
In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Projects Import page was possible
-
Medium 6.6
In JetBrains TeamCity before 2026.2 privilege escalation of project-scoped access tokens via concurrent project deletio…
-
Medium 6.5
In JetBrains TeamCity before 2026.2, 2026.1.4 arbitrary file write via read-write file channels in the Kotlin DSL sandb…
-
Medium 6.5
In JetBrains TeamCity before 2026.2.1 missing authorization allowed running modified build steps via pipeline debug runs
-
Medium 6.5
In JetBrains TeamCity before 2026.2.1 missing authorization allowed guests to push VCS labels using stored VCS credenti…
-
Medium 6.5
In JetBrains TeamCity before 2026.2.1 the build parameter editor allowed project settings viewers to recover protected …
-
Medium 6.5
In JetBrains TeamCity before 2026.2.1 missing authorization allowed reading VCS file contents and patches of other proj…
-
Medium 6.5
In JetBrains TeamCity before 2026.2.2 vCS root passwords could be extracted via the REST API property locator
-
Medium 6.5
In JetBrains TeamCity before 2026.2.2 a CSRF attack was possible on the diagnostic page
-
Medium 6.4
In JetBrains TeamCity before 2026.2 credential leakage via Mercurial subrepository URLs was possible
-
Medium 6.4
In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible
-
Medium 6.4
In JetBrains TeamCity before 2026.2.2 stored XSS in external change viewer links was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the unified diff page syntax highlighting was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS on the notification rules page was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in build problem details was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the build feature parameters page was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in the build log tree view was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Log page was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the inspection profile selector popup was pos…
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.5 reflected XSS on the Test History page was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2 reflected XSS in Kubernetes cloud profile namespace and deployment choosers was pos…
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Chains tab was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Clean-up Rules page was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the notification rule form was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the JVM update warning on the Agent Summary page was possib…
-
Medium 6.1
In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible
-
Medium 6.1
In JetBrains TeamCity before 2026.2.2, 2026.1.6 reflected XSS on the Edit VCS Root page was possible
-
Medium 5.9
In JetBrains TeamCity before 2026.2, 2026.1.4 authentication bypass via polling agent name rebinding was possible
-
Medium 5.9
In JetBrains TeamCity before 2026.2 improper authorization allowed project-limited access tokens to act with full permi…
-
Medium 5.9
In JetBrains TeamCity before 2026.2 privilege escalation to system administrator was possible via project administrator…
-
Medium 5.9
In JetBrains TeamCity before 2026.2 remote code execution on build agents was possible via service message injection in…
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed users with the Run build permission to del…
-
Medium 5.4
In JetBrains TeamCity before 2026.2 stored XSS in the duplicate remote parameter health report was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in Perforce job details was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the npm connection health report was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed project agent administrators to manage age…
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Triggers page was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Build Features page was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the artifact dependency tree was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the diff view page was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules path preview was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2 stored XSS on the Duplicates report tab was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in build statistics charts was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Large Build Log health report was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the project Report Tab dialog was possible
-
Medium 5.4
In JetBrains TeamCity before 2026.2.1 improper authorization allowed using AWS connections of other projects in cloud p…
-
Medium 5.3
In JetBrains TeamCity before 2026.2, 2026.1.4 unauthenticated extraction of build parameter values via a timing attack …
-
Medium 5.3
In JetBrains TeamCity before 2026.2 password parameters containing a caret were not masked in build logs on Windows
-
Medium 5.3
In JetBrains TeamCity before 2026.2.1 arbitrary file read was possible via symlinks in Mercurial subrepositories
-
Medium 4.9
In JetBrains TeamCity before 2026.2, 2026.1.4 the Perforce Administrator Access password could be written to the server…
-
Medium 4.9
In JetBrains TeamCity before 2026.2 project administrators could read OAuth connection secrets of ancestor projects
-
Medium 4.9
In JetBrains TeamCity before 2026.2.2, 2026.1.6 out-of-band data exfiltration via DNS resolution was possible in the Ko…
-
Medium 4.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in SSH key management was possible
-
Medium 4.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the queued build Overview tab was possible
-
Medium 4.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Pull Requests branch filter health report wa…
-
Medium 4.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the unknown VCS root page was possible
-
Medium 4.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Slack Notifier settings page was possible
-
Medium 4.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Versioned Settings page was possible
-
Medium 4.8
In JetBrains TeamCity before 2026.2 server certificates were not verified in the SVN integration
-
Medium 4.7
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the Xcode runner SDK selection was possible
-
Medium 4.4
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Test Details page was possible
-
Medium 4.3
In JetBrains TeamCity before 2026.2 missing authorization allowed reading Qodana reports of other projects
-
Medium 4.3
In JetBrains TeamCity before 2026.2, 2026.1.4 an SSRF via connection tests was possible for users without project edit …
-
Medium 4.3
In JetBrains TeamCity before 2026.2 missing authorization in statistics chart export allowed viewing data of project
-
Medium 4.3
In JetBrains TeamCity before 2026.2, 2026.1.4 missing authorization allowed users to remove all build configuration ass…
-
Medium 4.2
In JetBrains TeamCity before 2026.2 poisoning of OAuth discovery metadata via the X-Forwarded-Host header was possible
-
Low 3.7
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the notification rules editor was possible
-
Low 3.7
In JetBrains TeamCity before 2026.2.1, 2026.1.5 the TFS helper server was exposed on all network interfaces
-
Low 3.5
In JetBrains TeamCity before 2026.2 stored XSS on the build step settings page was possible
-
Low 3.5
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the Failure Conditions page was possible
-
Low 3.5
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in implicit agent requirements was possible
-
Low 3.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible
-
Low 3.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Slack connection test page was possible
-
Low 3.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the agent info popup was possible
-
Low 2.7
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 the Cloud Profiles page disclosed cloud profiles of projects t…
-
Low 2.7
In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI
-
Low 2.7
In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users
-
Low 2.7
In JetBrains TeamCity before 2026.2.2 the current request details debug endpoint exposed authentication headers and ses…
-
Low 2.4
In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via commit …
-
Low 2.4
In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via user an…
Revision history
-
#1
Initiale Fassung
References
-
JetBrains Fixed security issues vom 2026-11-19
https://www.jetbrains.com/privacy-security/issues-fixed/