Overview 93,253 matches · 6,179 in Waratek scope · 293 protected · 898 exploited · 187 CISA KEV · 920 public PoC · 80 EPSS ≥ 0.5
93,253matches
6,179in Waratek scope6.6%
293protected0.3%
898exploited1.0%
187CISA KEV0.2%
920public PoC1.0%
80EPSS ≥ 0.50.1%
Protected by Waratek
297
0.3%
Rule in development
0
0.0%
Mitigation candidate
28
0.0%
No exploit published
5,854
6.3%
Outside Waratek scope
162
0.2%
Not applicable
85,160
91.3%
Withdrawn CVE
1,752
1.9%
Critical
10,312
11.1%
High
38,596
41.4%
Medium
33,648
36.1%
Low
5,975
6.4%
None
37
0.0%
Unknown
4,685
5.0%
split by
peak 17,481 / month
Mar 266,304
Protected by Waratek12
Mitigation candidate6
No exploit published63
Outside Waratek scope44
Not applicable6,109
Withdrawn CVE70
Critical706
High2,637
Medium2,390
Low499
None2
Unknown70
blocked by ARMR today12
not blocked6,291
not established1
Exploited65
Working exploit published54
Proof of concept only1,830
No public exploit4,355
Apr 265,885
Protected by Waratek30
Mitigation candidate6
No exploit published157
Outside Waratek scope29
Not applicable5,588
Withdrawn CVE75
Critical595
High2,266
Medium2,407
Low542
Unknown75
blocked by ARMR today30
not blocked5,855
Exploited60
Working exploit published43
Proof of concept only1,847
Forecast only1
No public exploit3,934
May 266,985
Protected by Waratek27
Mitigation candidate2
No exploit published155
Outside Waratek scope11
Not applicable6,741
Withdrawn CVE49
Critical709
High2,875
Medium2,776
Low569
None7
Unknown49
blocked by ARMR today27
not blocked6,958
Exploited90
Working exploit published62
Proof of concept only1,769
No public exploit5,064
Jun 268,001
Protected by Waratek37
Mitigation candidate2
No exploit published442
Outside Waratek scope9
Not applicable7,452
Withdrawn CVE59
Critical990
High3,389
Medium3,039
Low520
None4
Unknown59
blocked by ARMR today37
not blocked7,964
Exploited104
Working exploit published44
Proof of concept only1,576
Forecast only1
No public exploit6,276
Jul 269,919
Protected by Waratek40
Mitigation candidate4
No exploit published1,139
Outside Waratek scope18
Not applicable8,570
Withdrawn CVE148
Critical1,376
High4,226
Medium3,569
Low587
None12
Unknown149
blocked by ARMR today38
partly blocked2
not blocked9,879
Exploited80
Working exploit published61
Proof of concept only1,769
No public exploit8,009
Aug 2612,719
Protected by Waratek40
Mitigation candidate5
No exploit published1,143
Outside Waratek scope6
Not applicable11,061
Withdrawn CVE464
Critical1,831
High5,294
Medium3,730
Low707
None5
Unknown1,152
blocked by ARMR today39
partly blocked1
not blocked12,679
Exploited111
Working exploit published49
Proof of concept only2,328
No public exploit10,231
Sep 2615,074
Protected by Waratek41
Mitigation candidate2
No exploit published924
Outside Waratek scope23
Not applicable13,937
Withdrawn CVE147
Critical1,544
High6,323
Medium4,888
Low913
None2
Unknown1,404
blocked by ARMR today41
not blocked15,033
Exploited118
Working exploit published36
Proof of concept only2,405
No public exploit12,515
Oct 2617,481
Protected by Waratek50
Mitigation candidate1
No exploit published1,138
Outside Waratek scope19
Not applicable15,843
Withdrawn CVE430
Critical1,628
High6,966
Medium6,602
Low986
None2
Unknown1,297
blocked by ARMR today50
not blocked17,431
Exploited150
Working exploit published25
Proof of concept only2,616
No public exploit14,690
Nov 2610,885
Protected by Waratek20
No exploit published693
Outside Waratek scope3
Not applicable9,859
Withdrawn CVE310
Critical933
High4,620
Medium4,247
Low652
None3
Unknown430
blocked by ARMR today19
partly blocked1
not blocked10,865
Exploited120
Working exploit published23
Proof of concept only1,138
No public exploit9,604
Mar 26Apr 26May 26Jun 26Jul 26Aug 26Sep 26Oct 26Nov 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-132991 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Slack connection test page was possible |
| CVE-2026-132990 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible |
| CVE-2026-132989 | Unknown | 2026-11-19 | Withdrawn CVE | No public exploit | |
| CVE-2026-132988 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 the Cloud Profiles page disclosed cloud profiles of projects the user could not access |
| CVE-2026-132987 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 server certificates were not verified in the SVN integration |
| CVE-2026-132986 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 password parameters containing a caret were not masked in build logs on Windows |
| CVE-2026-132985 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 project administrators could read OAuth connection secrets of ancestor projects |
| CVE-2026-132984 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the project Report Tab dialog was possible |
| CVE-2026-132983 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Report Tabs settings page was possible |
| CVE-2026-132982 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the build Report Tab dialog was possible |
| CVE-2026-132981 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Versioned Settings page was possible |
| CVE-2026-132980 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger branch filter settings was possible |
| CVE-2026-132979 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules editor was possible |
| CVE-2026-132978 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in agent requirements was possible |
| CVE-2026-132977 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Agent Statistics tooltip was possible |
| CVE-2026-132976 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Inspections (IntelliJ IDEA) build step editor was possible |
| CVE-2026-132975 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in issue tracker links was possible |
| CVE-2026-132974 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Promote build dialog for dependent builds was possible |
| CVE-2026-132973 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.5 stored XSS on the external Kotlin DSL editor status page was possible |
| CVE-2026-132972 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Slack Notifier settings page was possible |
| CVE-2026-132971 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger dependency settings was possible |
| CVE-2026-132970 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Finish Build Trigger editor was possible |
| CVE-2026-132969 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the Xcode runner configuration selection was possible |
| CVE-2026-132968 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Large Build Log health report was possible |
| CVE-2026-132967 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the build Issues tab was possible |
| CVE-2026-132966 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in build statistics charts was possible |
| CVE-2026-132965 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the unknown VCS root page was possible |
| CVE-2026-132964 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 stored XSS on the Duplicates report tab was possible |
| CVE-2026-132963 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules path preview was possible |
| CVE-2026-132962 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the JVM update warning on the Agent Summary page was possible |
| CVE-2026-132961 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Test Details page was possible |
| CVE-2026-132960 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the diff view page was possible |
| CVE-2026-132959 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 remote code execution on build agents was possible via service message injection in build configuration names |
| CVE-2026-132958 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the artifact dependency tree was possible |
| CVE-2026-132957 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the configuration health popup was possible |
| CVE-2026-132956 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Build Features page was possible |
| CVE-2026-132955 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Pull Requests branch filter health report was possible |
| CVE-2026-132954 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Triggers page was possible |
| CVE-2026-132953 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the queued build Overview tab was possible |
| CVE-2026-132952 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 privilege escalation to system administrator was possible via project administrator roles in simple authorization mode |
| CVE-2026-132951 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the notification rule form was possible |
| CVE-2026-132950 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the Xcode runner SDK selection was possible |
| CVE-2026-132949 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Clean-up Rules page was possible |
| CVE-2026-132948 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Chains tab was possible |
| CVE-2026-132947 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 reflected XSS in Kubernetes cloud profile namespace and deployment choosers was possible |
| CVE-2026-132946 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.5 reflected XSS on the Test History page was possible |
| CVE-2026-132945 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the inspection profile selector popup was possible |
| CVE-2026-132944 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed project agent administrators to manage agents of other projects |
| CVE-2026-132943 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Log page was possible |
| CVE-2026-132942 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 unauthenticated extraction of build parameter values via a timing attack on build status icons was possible |
| CVE-2026-132941 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 missing authorization allowed users to remove all build configuration assignments from an agent |
| CVE-2026-132940 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 credential leakage via Mercurial subrepository URLs was possible |
| CVE-2026-132939 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Maven settings health report was possible |
| CVE-2026-132938 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 improper authorization allowed project-limited access tokens to act with full permissions via XML-RPC |
| CVE-2026-132937 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 arbitrary file write via read-write file channels in the Kotlin DSL sandbox was possible |
| CVE-2026-132936 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the npm connection health report was possible |
| CVE-2026-132935 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 missing authorization in statistics chart export allowed viewing data of project |
| CVE-2026-132934 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 authentication bypass via polling agent name rebinding was possible |
| CVE-2026-132933 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 privilege escalation of project-scoped access tokens via concurrent project deletion was possible |
| CVE-2026-132932 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in the build log tree view was possible |
| CVE-2026-132931 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the build feature parameters page was possible |
| CVE-2026-132930 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in build problem details was possible |
| CVE-2026-132929 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS on the notification rules page was possible |
| CVE-2026-132928 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in Perforce job details was possible |
| CVE-2026-132927 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 the Perforce Administrator Access password could be written to the server log |
| CVE-2026-132926 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 poisoning of OAuth discovery metadata via the X-Forwarded-Host header was possible |
| CVE-2026-132925 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 stored XSS in the duplicate remote parameter health report was possible |
| CVE-2026-132924 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed users with the Run build permission to delete Perforce workspaces |
| CVE-2026-132923 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in SSH key management was possible |
| CVE-2026-132922 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the unified diff page syntax highlighting was possible |
| CVE-2026-132921 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 two-factor authentication bypass was possible via access token management |
| CVE-2026-132920 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 an SSRF via connection tests was possible for users without project edit permissions |
| CVE-2026-132919 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 missing authorization allowed reading Qodana reports of other projects |
| CVE-2026-132918 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on build and queue pages was possible |
| CVE-2026-132917 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via a file write bypass in the Kotlin DSL sandbox |
| CVE-2026-132916 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 arbitrary file deletion on the server was possible via the Kotlin DSL sandbox |
| CVE-2026-132915 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an LDAP injection allowed bypassing login restrictions |
| CVE-2026-132914 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Issue Log tab was possible |
| CVE-2026-132913 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the P4 Code Review build tab was possible |
| CVE-2026-132912 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via class injection in the Kotlin DSL sandbox |
| CVE-2026-132911 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via build access codes disclosed to project users |
| CVE-2026-132910 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 unauthenticated DoS via the agent protocol was possible |
| CVE-2026-132909 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial repository contents |
| CVE-2026-132908 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial VCS root settings |
| CVE-2026-132907 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 project viewers could redirect GitHub App connection credentials of parent projects |
| CVE-2026-132906 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via native code loading in the Kotlin DSL sandbox |
| CVE-2026-132905 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the AWS Credentials build feature was possible |
| CVE-2026-132904 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 missing authorization allowed project viewers to remove VCS roots |
| CVE-2026-132903 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 missing authorization allowed any authenticated user to start and stop cloud agent instances |
| CVE-2026-132902 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 access keys of parent project AWS connections could be disclosed |
| CVE-2026-132901 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 improper authorization allowed publishing packages to NuGet feeds of other projects |
| CVE-2026-132900 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 secure parameter values were disclosed to project viewers in pipelines |
| CVE-2026-132899 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the NPM Registry build feature was possible |
| CVE-2026-132898 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 arbitrary file write on the server was possible via Kotlin DSL settings |
| CVE-2026-132897 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 improper authorization allowed access to credentials of other projects via build configuration settings |
| CVE-2026-132896 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 remote code execution was possible via Kubernetes Executor settings |
| CVE-2026-132895 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Subversion VCS root settings |
| CVE-2026-132894 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an SSRF in AWS connection settings could expose server credentials |
| CVE-2026-132893 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an SSRF via pipeline repository branch listing was possible |
| CVE-2026-132892 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 privilege escalation was possible via the authorization flow |