Overview 160,710 matches · 7,244 in Waratek scope · 434 protected · 1,878 exploited · 448 CISA KEV · 2,358 public PoC · 337 EPSS ≥ 0.5
160,710matches
7,244in Waratek scope4.5%
434protected0.3%
1,878exploited1.2%
448CISA KEV0.3%
2,358public PoC1.5%
337EPSS ≥ 0.50.2%
Protected by Waratek
438
0.3%
Rule in development
4
0.0%
Mitigation candidate
59
0.0%
No exploit published
6,743
4.2%
Outside Waratek scope
356
0.2%
Not applicable
148,456
92.4%
Withdrawn CVE
4,654
2.9%
Critical
16,530
10.3%
High
61,363
38.2%
Medium
64,290
40.0%
Low
9,866
6.1%
None
78
0.0%
Unknown
8,583
5.3%
split by
peak 37,712 / quarter
Q4 247,534
Protected by Waratek17
Mitigation candidate3
No exploit published61
Outside Waratek scope37
Not applicable7,369
Withdrawn CVE47
Critical771
High2,768
Medium3,806
Low139
Unknown50
blocked by ARMR today17
not blocked7,517
Exploited97
Working exploit published59
Proof of concept only1,124
Forecast only5
No public exploit6,249
Q1 2512,412
Protected by Waratek21
Mitigation candidate4
No exploit published151
Outside Waratek scope23
Not applicable11,747
Withdrawn CVE466
Critical1,155
High4,302
Medium6,190
Low299
Unknown466
blocked by ARMR today21
not blocked12,391
Exploited171
Working exploit published138
Proof of concept only2,410
Forecast only7
No public exploit9,686
Q2 2512,205
Protected by Waratek32
Rule in development1
Mitigation candidate8
No exploit published153
Outside Waratek scope31
Not applicable11,470
Withdrawn CVE510
Critical1,093
High3,931
Medium6,106
Low559
None6
Unknown510
blocked by ARMR today32
not blocked12,173
Exploited196
Working exploit published89
Proof of concept only2,808
Forecast only9
No public exploit9,103
Q3 2512,207
Protected by Waratek23
Rule in development1
Mitigation candidate6
No exploit published238
Outside Waratek scope39
Not applicable11,418
Withdrawn CVE482
Critical1,205
High3,992
Medium5,277
Low1,250
None1
Unknown482
blocked by ARMR today23
not blocked12,184
Exploited194
Working exploit published295
Proof of concept only3,016
Forecast only1
No public exploit8,701
Q4 2513,148
Protected by Waratek27
Rule in development2
Mitigation candidate7
No exploit published189
Outside Waratek scope46
Not applicable12,513
Withdrawn CVE364
Critical1,037
High4,445
Medium5,470
Low932
None3
Unknown1,261
blocked by ARMR today27
not blocked13,119
not established2
Exploited185
Working exploit published71
Proof of concept only2,746
No public exploit10,146
Q1 2616,255
Protected by Waratek33
Mitigation candidate9
No exploit published160
Outside Waratek scope62
Not applicable14,888
Withdrawn CVE1,103
Critical1,663
High5,966
Medium6,183
Low1,211
None33
Unknown1,199
blocked by ARMR today33
not blocked16,221
not established1
Exploited202
Working exploit published134
Proof of concept only4,213
Forecast only3
No public exploit11,703
Q2 2620,871
Protected by Waratek94
Mitigation candidate10
No exploit published754
Outside Waratek scope49
Not applicable19,781
Withdrawn CVE183
Critical2,294
High8,530
Medium8,222
Low1,631
None11
Unknown183
blocked by ARMR today94
not blocked20,777
Exploited254
Working exploit published149
Proof of concept only5,192
Forecast only2
No public exploit15,274
Q3 2637,712
Protected by Waratek121
Mitigation candidate11
No exploit published3,206
Outside Waratek scope47
Not applicable33,568
Withdrawn CVE759
Critical4,751
High15,843
Medium12,187
Low2,207
None19
Unknown2,705
blocked by ARMR today118
partly blocked3
not blocked37,591
Exploited309
Working exploit published146
Proof of concept only6,502
No public exploit30,755
Q4 2628,366
Protected by Waratek70
Mitigation candidate1
No exploit published1,831
Outside Waratek scope22
Not applicable25,702
Withdrawn CVE740
Critical2,561
High11,586
Medium10,849
Low1,638
None5
Unknown1,727
blocked by ARMR today69
partly blocked1
not blocked28,296
Exploited270
Working exploit published48
Proof of concept only3,754
No public exploit24,294
Q4 24Q1 25Q2 25Q3 25Q4 25Q1 26Q2 26Q3 26Q4 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 |