Overview 176,195 matches · 8,336 in Waratek scope · 532 protected · 1,017 exploited · 183 CISA KEV · 11,846 public PoC · 701 EPSS ≥ 0.5
176,195matches
8,336in Waratek scope4.7%
532protected0.3%
1,017exploited0.6%
183CISA KEV0.1%
11,846public PoC6.7%
701EPSS ≥ 0.50.4%
Protected by Waratek
534
0.3%
Rule in development
2
0.0%
Mitigation candidate
218
0.1%
No exploit published
7,582
4.3%
Outside Waratek scope
1,746
1.0%
Not applicable
166,113
94.3%
Withdrawn CVE
0
0.0%
split by
peak 37,441 / year
19891
Not applicable1
Medium1
not blocked1
No public exploit1
19902
Not applicable2
Medium2
not blocked2
Working exploit published1
No public exploit1
19914
Not applicable4
Medium4
not blocked4
No public exploit4
19920
19933
Not applicable3
Medium3
not blocked3
No public exploit3
199410
Not applicable10
Medium10
not blocked10
Working exploit published2
No public exploit8
19956
Not applicable6
Medium6
not blocked6
Working exploit published2
No public exploit4
199621
Not applicable21
Medium21
not blocked21
Working exploit published5
No public exploit16
199789
Not applicable89
Medium89
not blocked89
Working exploit published18
No public exploit71
199885
Not applicable85
Medium85
not blocked85
Working exploit published11
No public exploit74
1999357
Outside Waratek scope1
Not applicable356
Medium357
not blocked357
Working exploit published119
No public exploit238
2000467
Mitigation candidate4
No exploit published3
Not applicable460
Medium467
not blocked467
Exploited2
Working exploit published195
No public exploit270
2001706
Mitigation candidate3
No exploit published5
Outside Waratek scope5
Not applicable693
Medium706
not blocked706
Exploited3
Working exploit published219
Forecast only2
No public exploit482
2002980
Protected by Waratek2
Mitigation candidate6
No exploit published16
Outside Waratek scope1
Not applicable955
Medium980
blocked by ARMR today2
not blocked978
Exploited3
Working exploit published246
Forecast only3
No public exploit728
2003747
Protected by Waratek2
Mitigation candidate5
No exploit published18
Not applicable722
Medium747
blocked by ARMR today2
not blocked745
Working exploit published243
No public exploit504
20041,265
Protected by Waratek1
Mitigation candidate1
No exploit published16
Outside Waratek scope4
Not applicable1,243
Medium1,265
blocked by ARMR today1
not blocked1,264
Exploited10
Working exploit published414
Forecast only1
No public exploit840
20052,430
Protected by Waratek3
Mitigation candidate4
No exploit published40
Outside Waratek scope5
Not applicable2,378
Medium2,430
blocked by ARMR today3
not blocked2,427
Exploited8
Working exploit published622
Forecast only6
No public exploit1,794
20063,324
Protected by Waratek4
Mitigation candidate4
No exploit published49
Outside Waratek scope2
Not applicable3,265
Medium3,324
blocked by ARMR today4
not blocked3,320
Exploited12
Working exploit published1,135
Forecast only2
No public exploit2,175
20073,101
Protected by Waratek3
Mitigation candidate11
No exploit published67
Outside Waratek scope42
Not applicable2,978
Medium3,101
blocked by ARMR today3
not blocked3,098
Exploited14
Working exploit published1,052
Forecast only1
No public exploit2,034
20082,582
Protected by Waratek4
Mitigation candidate8
No exploit published73
Outside Waratek scope23
Not applicable2,474
Medium2,582
blocked by ARMR today4
not blocked2,578
Exploited7
Working exploit published987
Proof of concept only2
Forecast only1
No public exploit1,585
20092,786
Protected by Waratek5
Mitigation candidate9
No exploit published121
Outside Waratek scope25
Not applicable2,626
Medium2,786
blocked by ARMR today5
not blocked2,781
Exploited17
Working exploit published1,122
Proof of concept only2
Forecast only3
No public exploit1,642
20102,241
Protected by Waratek6
Mitigation candidate10
No exploit published118
Outside Waratek scope33
Not applicable2,074
Medium2,241
blocked by ARMR today6
not blocked2,235
Exploited14
Working exploit published547
Proof of concept only1
Forecast only2
No public exploit1,677
20112,101
Protected by Waratek4
Mitigation candidate4
No exploit published156
Outside Waratek scope33
Not applicable1,904
Medium2,101
blocked by ARMR today4
not blocked2,097
Exploited9
Working exploit published294
Proof of concept only3
Forecast only1
No public exploit1,794
20123,035
Protected by Waratek5
Mitigation candidate20
No exploit published187
Outside Waratek scope35
Not applicable2,788
Medium3,035
blocked by ARMR today5
not blocked3,029
not established1
Exploited20
Working exploit published475
Proof of concept only2
Forecast only42
No public exploit2,496
20132,914
Protected by Waratek12
Mitigation candidate13
No exploit published234
Outside Waratek scope144
Not applicable2,511
Medium2,914
blocked by ARMR today12
not blocked2,901
not established1
Exploited23
Working exploit published237
Proof of concept only1
Forecast only6
No public exploit2,647
20145,314
Protected by Waratek32
Mitigation candidate9
No exploit published224
Outside Waratek scope150
Not applicable4,899
Medium5,314
blocked by ARMR today32
not blocked5,282
Exploited24
Working exploit published415
Proof of concept only7
Forecast only12
No public exploit4,856
20153,501
Protected by Waratek20
Mitigation candidate2
No exploit published222
Outside Waratek scope107
Not applicable3,150
Medium3,501
blocked by ARMR today20
not blocked3,481
Exploited24
Working exploit published254
Proof of concept only7
Forecast only8
No public exploit3,208
20162,446
Protected by Waratek26
Mitigation candidate3
No exploit published297
Outside Waratek scope45
Not applicable2,075
Medium2,446
blocked by ARMR today26
not blocked2,419
not established1
Exploited16
Working exploit published122
Proof of concept only6
Forecast only9
No public exploit2,293
20175,687
Protected by Waratek24
Mitigation candidate5
No exploit published336
Outside Waratek scope110
Not applicable5,212
Medium5,687
blocked by ARMR today24
not blocked5,663
Exploited18
Working exploit published332
Proof of concept only21
Forecast only2
No public exploit5,314
20186,163
Protected by Waratek54
Mitigation candidate13
No exploit published444
Outside Waratek scope82
Not applicable5,570
Medium6,163
blocked by ARMR today54
not blocked6,109
Exploited38
Working exploit published348
Proof of concept only27
Forecast only7
No public exploit5,743
20197,117
Protected by Waratek35
Mitigation candidate17
No exploit published427
Outside Waratek scope116
Not applicable6,522
Medium7,117
blocked by ARMR today34
partly blocked1
not blocked7,082
Exploited47
Working exploit published297
Proof of concept only30
Forecast only8
No public exploit6,735
20207,359
Protected by Waratek35
Mitigation candidate17
No exploit published517
Outside Waratek scope131
Not applicable6,659
Medium7,359
blocked by ARMR today35
not blocked7,324
Exploited58
Working exploit published197
Proof of concept only37
Forecast only10
No public exploit7,057
20218,137
Protected by Waratek29
Mitigation candidate12
No exploit published301
Outside Waratek scope159
Not applicable7,636
Medium8,137
blocked by ARMR today29
not blocked8,108
Exploited88
Working exploit published240
Proof of concept only90
Forecast only43
No public exploit7,676
20229,908
Protected by Waratek58
Mitigation candidate3
No exploit published575
Outside Waratek scope113
Not applicable9,159
Medium9,908
blocked by ARMR today58
not blocked9,850
Exploited73
Working exploit published270
Proof of concept only953
Forecast only34
No public exploit8,578
202311,824
Protected by Waratek29
Mitigation candidate10
No exploit published441
Outside Waratek scope96
Not applicable11,248
Medium11,824
blocked by ARMR today29
not blocked11,795
Exploited99
Working exploit published237
Proof of concept only2,407
Forecast only26
No public exploit9,055
202418,998
Protected by Waratek19
Mitigation candidate5
No exploit published322
Outside Waratek scope110
Not applicable18,542
Medium18,998
blocked by ARMR today19
not blocked18,979
Exploited129
Working exploit published114
Proof of concept only3,597
Forecast only10
No public exploit15,148
202523,043
Protected by Waratek37
Rule in development2
Mitigation candidate14
No exploit published473
Outside Waratek scope78
Not applicable22,439
Medium23,043
blocked by ARMR today37
not blocked23,006
Exploited133
Working exploit published170
Proof of concept only5,242
Forecast only5
No public exploit17,493
202637,441
Protected by Waratek85
Mitigation candidate6
No exploit published1,900
Outside Waratek scope96
Not applicable35,354
Medium37,441
blocked by ARMR today84
partly blocked1
not blocked37,356
Exploited128
Working exploit published124
Proof of concept only6,895
No public exploit30,294
1990199319961999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-91139 | Medium | 2026-11-19 | Not applicable | No public exploit | Deco BE65 firmware contains a cryptographic weakness in the local web-management authentication flow due to the use of insufficient RSA key sizes. The /login?form=auth endpoint returns a 512-bit RSA public key and sequence value. Successful exploitation may compromise the cryptographic protections applied to local web-management authentication traffic. |
| CVE-2026-91138 | Medium | 2026-11-19 | Not applicable | No public exploit | The Deco BE65 v3 firmware contains a shared hard-coded password hash for the root account in /etc/shadow. Where the corresponding credential is accepted by a production authentication path, an attacker with existing unprivileged shell access may recover or otherwise obtain the plaintext password and use it to escalate privileges. Successful exploitation may grant root-level access to the affected device. |
| CVE-2026-87956 | Medium | 2026-11-19 | Not applicable | No public exploit | When Private data source connect (PDC) or a secure SOCKS proxy is used, the MQTT data source plugin does not apply TLS to broker connections for the tls, ssl, tcps, mqtts and mqtt+ssl schemes. The configured TLS settings are ignored, and the broker username and password are sent unencrypted on the hop between the proxy and the broker. The server certificate is not verified, and a configured client certificate is not sent. |
| CVE-2026-85413 | Medium | 2026-11-19 | Not applicable | No public exploit | The Foxtool All-in-One: Contact chat button, Custom login, Media optimize images plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'foxtool_image_id' parameter in all versions up to, and including, 2.5.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A subscriber-level attacker can store a payload in their own profile's foxtoolpic user-meta that executes in an administrator's browser session when the administrator views the user via the Users → Edit screen. |
| CVE-2026-2307 | Medium | 2026-11-19 | Not applicable | No public exploit | The Elementor Website Builder – More Than Just a Page Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.0.5 via `/wp-json/elementor/v1/user` REST endpoint. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive data including emails, password hashes and usernames for all WordPress users. |
| CVE-2026-19865 | Medium | 2026-11-19 | Not applicable | No public exploit | Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to limit the aggregate memory allocated when processing ZIP archive entries during document content extraction and Slack workspace import, which allows an authenticated attacker to cause a server-side denial of service via a crafted ZIP archive.. Mattermost Advisory ID: MMSA-2026-00772 |
| CVE-2026-133106 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Projects Import page was possible |
| CVE-2026-133105 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 reflected XSS on the Edit VCS Root page was possible |
| CVE-2026-133104 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2 stored XSS in external change viewer links was possible |
| CVE-2026-133103 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in the enforced settings restriction tooltip was possible |
| CVE-2026-133102 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 out-of-band data exfiltration via DNS resolution was possible in the Kotlin DSL sandbox |
| CVE-2026-133101 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2 a CSRF attack was possible on the diagnostic page |
| CVE-2026-133100 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 command injection in Project Import artifact copy scripts was possible |
| CVE-2026-133099 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2 vCS root passwords could be extracted via the REST API property locator |
| CVE-2026-133098 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2 stored XSS in GitHub issue tracker suggestions was possible |
| CVE-2026-133054 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Create Project dialog was possible |
| CVE-2026-133053 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 arbitrary file read was possible via symlinks in Mercurial subrepositories |
| CVE-2026-133052 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 a DOM-based XSS in the plugin installation dialog was possible |
| CVE-2026-133051 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the JaCoCo coverage settings was possible |
| CVE-2026-133050 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored and reflected XSS in Space project connection dialogs was possible |
| CVE-2026-133049 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for VCS roots was possible |
| CVE-2026-133048 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 improper authorization allowed using AWS connections of other projects in cloud profiles |
| CVE-2026-133047 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the thread dump page was possible |
| CVE-2026-133046 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS in recipe export errors was possible |
| CVE-2026-133045 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS in VMware vSphere cloud profile settings was possible |
| CVE-2026-133043 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 missing authorization allowed reading VCS file contents and patches of other projects |
| CVE-2026-133042 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS in the Amazon EC2 cloud profile editor was possible |
| CVE-2026-133041 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible |
| CVE-2026-133039 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for Space connections was possible |
| CVE-2026-133038 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS in the Maven Build Info project header was possible |
| CVE-2026-133037 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the GitHub App repository selector was possible |
| CVE-2026-133036 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS in the Issue Trackers health report was possible |
| CVE-2026-133035 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS on the change Files tab was possible |
| CVE-2026-133034 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible |
| CVE-2026-133033 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS in Maven Build Info module links was possible |
| CVE-2026-133032 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible |
| CVE-2026-133031 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible |
| CVE-2026-133030 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 the build parameter editor allowed project settings viewers to recover protected credentials |
| CVE-2026-133029 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 missing authorization allowed guests to push VCS labels using stored VCS credentials |
| CVE-2026-133028 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 missing authorization allowed running modified build steps via pipeline debug runs |
| CVE-2026-133001 | Medium | 2026-11-19 | Not applicable | No public exploit | FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector's current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector's scope was narrowed or changed. This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts. Security impact: - Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope. - Stale access persists indefinitely until the alert is independently re-scoped or deleted. Affected version: <4.1.0. |
| 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 |