363 sonuç
3.1Düşük
CVE-2026-132251
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3 privilege escalation was possible by issuing new tokens from a restricted access token

3.1Düşük
CVE-2026-132250
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3 privilege escalation was possible via Basic authentication with a restricted access token

4.8Orta
CVE-2026-132249
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Shared Resources build feature was possible

5.4Orta
CVE-2026-132248
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3 improper authorization allowed project viewers to change project IDs

4.3Orta
CVE-2026-132247
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 improper authorization allowed viewing build process details via agent stacktraces

6.6Orta
CVE-2026-132246
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 privilege escalation to system administrator was possible after disabling per-project permissions

7.5Yüksek
CVE-2026-132245
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 DoS via agent command results was possible

8.1Yüksek
CVE-2026-132244
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS on the Disk Usage and Build Time pages was possible

7.6Yüksek
CVE-2026-132243
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS on the Docker Container Info tab was possible

7.6Yüksek
CVE-2026-132242
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Promote build dialog was possible

7.7Yüksek
CVE-2026-132238
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.8 disclosure of password parameter values to project viewers was possible

8.8Yüksek
CVE-2026-132237
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in the external artifact cache

8.8Yüksek
CVE-2026-132236
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in the pipeline YAML file path

7.2Yüksek
CVE-2026-132235
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in project import archives

9.9Kritik
CVE-2026-132234
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Mercurial VCS root settings

9.9Kritik
CVE-2026-132233
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via build attribute injection

9.9Kritik
CVE-2026-132232
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Perforce settings

9.9Kritik
CVE-2026-132231
JetBrains TeamCity

In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via best-fit character mapping in Perforce settings

4.4Orta
CVE-2026-123858
JetBrains PhpStorm

In JetBrains PhpStorm before 2026.3 project files could be automatically uploaded to a deployment server from untrusted projects

4.3Orta
CVE-2026-123857
JetBrains PhpStorm

In JetBrains PhpStorm before 2026.3 xXE was possible in untrusted projects via PHPMD ruleset autodetection

6.5Orta
CVE-2026-123856
JetBrains Toolbox App

In JetBrains Toolbox App before 3.6.1 nTLM hash disclosure was possible via SVG tool icons from a Remote Development server

7.5Yüksek
CVE-2026-123855
JetBrains Toolbox App

In JetBrains Toolbox App before 3.6.1 command injection was possible via enterprise configuration URLs

5.5Orta
CVE-2026-123854
JetBrains PyCharm

In JetBrains PyCharm before 2026.3 code execution was possible in Safe Mode via a crafted Jupyter notebook widget module

7.8Yüksek
CVE-2026-123853
JetBrains IntelliJ IDEA

In JetBrains IntelliJ IDEA before 2026.3, 2026.2.2 code execution was possible in Safe Mode via project-controlled JVM options of the build process

7.4Yüksek
CVE-2026-123852
JetBrains Junie GitHub Action

In JetBrains Junie GitHub Action before 1.8.0 code execution with workflow credentials was possible via fork updates