Overview 428,336 matches · 18,057 in Waratek scope · 1,813 protected · 5,967 exploited · 1,786 CISA KEV · 31,242 public PoC · 4,387 EPSS ≥ 0.5
428,336matches
18,057in Waratek scope4.2%
1,813protected0.4%
5,967exploited1.4%
1,786CISA KEV0.4%
31,242public PoC7.3%
4,387EPSS ≥ 0.51.0%
Protected by Waratek
1,828
0.4%
Rule in development
7
0.0%
Mitigation candidate
460
0.1%
No exploit published
15,762
3.7%
Outside Waratek scope
3,536
0.8%
Not applicable
387,559
90.5%
Withdrawn CVE
19,184
4.5%
Critical
44,274
10.3%
High
166,509
38.9%
Medium
176,099
41.1%
Low
18,109
4.2%
None
79
0.0%
Unknown
23,266
5.4%
split by
peak 103,204 / year
199639
Not applicable39
Critical1
High24
Medium12
Low2
not blocked39
Working exploit published10
No public exploit29
1997253
Not applicable252
Withdrawn CVE1
Critical1
High143
Medium89
Low19
Unknown1
not blocked253
Exploited2
Working exploit published73
Forecast only2
No public exploit176
1998247
Not applicable246
Withdrawn CVE1
Critical1
High137
Medium85
Low23
Unknown1
not blocked247
Exploited1
Working exploit published50
No public exploit196
1999923
No exploit published2
Outside Waratek scope1
Not applicable891
Withdrawn CVE29
Critical3
High423
Medium357
Low111
Unknown29
not blocked923
Exploited2
Working exploit published282
No public exploit639
20001,020
Mitigation candidate7
No exploit published7
Not applicable1,005
Withdrawn CVE1
Critical2
High454
Medium467
Low96
Unknown1
not blocked1,020
Exploited5
Working exploit published427
Forecast only1
No public exploit587
20011,679
Protected by Waratek1
Mitigation candidate4
No exploit published11
Outside Waratek scope10
Not applicable1,650
Withdrawn CVE3
Critical12
High776
Medium706
Low182
Unknown3
blocked by ARMR today1
not blocked1,678
Exploited14
Working exploit published480
Forecast only2
No public exploit1,183
20022,170
Protected by Waratek3
Mitigation candidate8
No exploit published28
Outside Waratek scope4
Not applicable2,113
Withdrawn CVE14
Critical10
High1,023
Medium980
Low143
Unknown14
blocked by ARMR today3
not blocked2,167
Exploited12
Working exploit published545
Forecast only9
No public exploit1,604
20031,548
Protected by Waratek2
Mitigation candidate8
No exploit published31
Outside Waratek scope4
Not applicable1,482
Withdrawn CVE21
Critical9
High674
Medium747
Low97
Unknown21
blocked by ARMR today2
not blocked1,546
Exploited10
Working exploit published499
Forecast only1
No public exploit1,038
20042,479
Protected by Waratek3
Mitigation candidate1
No exploit published25
Outside Waratek scope5
Not applicable2,417
Withdrawn CVE28
Critical10
High973
Medium1,265
Low203
Unknown28
blocked by ARMR today3
not blocked2,476
Exploited21
Working exploit published755
Forecast only1
No public exploit1,702
20055,010
Protected by Waratek3
Mitigation candidate5
No exploit published76
Outside Waratek scope15
Not applicable4,833
Withdrawn CVE78
Critical13
High2,048
Medium2,430
Low441
Unknown78
blocked by ARMR today3
not blocked5,007
Exploited22
Working exploit published1,341
Forecast only11
No public exploit3,636
20066,659
Protected by Waratek8
Mitigation candidate5
No exploit published127
Outside Waratek scope54
Not applicable6,414
Withdrawn CVE51
Critical12
High2,763
Medium3,324
Low509
Unknown51
blocked by ARMR today8
not blocked6,651
Exploited37
Working exploit published2,440
Proof of concept only1
Forecast only6
No public exploit4,175
20076,596
Protected by Waratek7
Mitigation candidate13
No exploit published146
Outside Waratek scope66
Not applicable6,284
Withdrawn CVE80
Critical21
High3,162
Medium3,101
Low232
Unknown80
blocked by ARMR today7
not blocked6,589
Exploited47
Working exploit published2,495
Proof of concept only5
Forecast only5
No public exploit4,044
20085,664
Protected by Waratek7
Mitigation candidate11
No exploit published134
Outside Waratek scope51
Not applicable5,429
Withdrawn CVE32
Critical19
High2,846
Medium2,582
Low185
Unknown32
blocked by ARMR today7
not blocked5,657
Exploited42
Working exploit published2,518
Proof of concept only4
Forecast only9
No public exploit3,091
20095,778
Protected by Waratek9
Mitigation candidate16
No exploit published195
Outside Waratek scope45
Not applicable5,467
Withdrawn CVE46
Critical15
High2,734
Medium2,786
Low197
Unknown46
blocked by ARMR today9
not blocked5,769
Exploited73
Working exploit published2,591
Proof of concept only2
Forecast only3
No public exploit3,109
20104,667
Protected by Waratek9
Mitigation candidate14
No exploit published168
Outside Waratek scope74
Not applicable4,374
Withdrawn CVE28
Critical28
High2,093
Medium2,241
Low277
Unknown28
blocked by ARMR today9
not blocked4,658
Exploited73
Working exploit published1,313
Proof of concept only1
Forecast only9
No public exploit3,271
20114,172
Protected by Waratek6
Mitigation candidate13
No exploit published205
Outside Waratek scope83
Not applicable3,843
Withdrawn CVE22
Critical5
High1,784
Medium2,101
Low260
Unknown22
blocked by ARMR today6
not blocked4,166
Exploited50
Working exploit published691
Proof of concept only5
Forecast only4
No public exploit3,422
20125,351
Protected by Waratek9
Mitigation candidate26
No exploit published291
Outside Waratek scope76
Not applicable4,886
Withdrawn CVE63
Critical21
High1,724
Medium3,035
Low508
Unknown63
blocked by ARMR today9
not blocked5,340
not established2
Exploited59
Working exploit published831
Proof of concept only7
Forecast only46
No public exploit4,408
20135,324
Protected by Waratek26
Mitigation candidate19
No exploit published318
Outside Waratek scope284
Not applicable4,540
Withdrawn CVE137
Critical23
High1,735
Medium2,914
Low515
Unknown137
blocked by ARMR today26
not blocked5,297
not established1
Exploited97
Working exploit published520
Proof of concept only3
Forecast only21
No public exploit4,683
20148,008
Protected by Waratek41
Mitigation candidate13
No exploit published292
Outside Waratek scope233
Not applicable7,349
Withdrawn CVE80
Critical20
High1,938
Medium5,314
Low656
Unknown80
blocked by ARMR today41
not blocked7,967
Exploited97
Working exploit published795
Proof of concept only13
Forecast only16
No public exploit7,087
20156,595
Protected by Waratek33
Mitigation candidate7
No exploit published308
Outside Waratek scope171
Not applicable5,975
Withdrawn CVE101
Critical51
High2,354
Medium3,501
Low588
Unknown101
blocked by ARMR today33
not blocked6,562
Exploited96
Working exploit published647
Proof of concept only16
Forecast only19
No public exploit5,817
20166,517
Protected by Waratek61
Mitigation candidate10
No exploit published479
Outside Waratek scope108
Not applicable5,791
Withdrawn CVE68
Critical887
High2,895
Medium2,446
Low221
Unknown68
blocked by ARMR today59
partly blocked2
not blocked6,455
not established1
Exploited103
Working exploit published429
Proof of concept only27
Forecast only32
No public exploit5,926
201718,113
Protected by Waratek108
Mitigation candidate15
No exploit published701
Outside Waratek scope212
Not applicable13,606
Withdrawn CVE3,471
Critical2,113
High6,608
Medium5,687
Low234
Unknown3,471
blocked by ARMR today104
partly blocked4
not blocked18,005
Exploited212
Working exploit published1,259
Proof of concept only52
Forecast only23
No public exploit16,567
201818,154
Protected by Waratek183
Mitigation candidate23
No exploit published724
Outside Waratek scope205
Not applicable15,375
Withdrawn CVE1,644
Critical2,616
High7,571
Medium6,163
Low160
Unknown1,644
blocked by ARMR today182
partly blocked1
not blocked17,971
Exploited236
Working exploit published1,069
Proof of concept only87
Forecast only34
No public exploit16,728
201918,938
Protected by Waratek123
Rule in development1
Mitigation candidate32
No exploit published797
Outside Waratek scope262
Not applicable16,090
Withdrawn CVE1,633
Critical2,657
High7,227
Medium7,117
Low304
Unknown1,633
blocked by ARMR today121
partly blocked2
not blocked18,813
not established2
Exploited327
Working exploit published784
Proof of concept only126
Forecast only51
No public exploit17,650
202019,222
Protected by Waratek157
Mitigation candidate38
No exploit published943
Outside Waratek scope263
Not applicable16,921
Withdrawn CVE900
Critical2,780
High7,782
Medium7,359
Low401
Unknown900
blocked by ARMR today157
not blocked19,065
Exploited344
Working exploit published602
Proof of concept only156
Forecast only66
No public exploit18,054
202121,950
Protected by Waratek124
Rule in development1
Mitigation candidate28
No exploit published669
Outside Waratek scope331
Not applicable18,996
Withdrawn CVE1,801
Critical2,850
High8,770
Medium8,137
Low392
Unknown1,801
blocked by ARMR today124
not blocked21,826
Exploited490
Working exploit published446
Proof of concept only217
Forecast only167
No public exploit20,630
202226,431
Protected by Waratek215
Rule in development1
Mitigation candidate20
No exploit published901
Outside Waratek scope269
Not applicable23,667
Withdrawn CVE1,358
Critical4,441
High10,337
Medium9,908
Low385
Unknown1,360
blocked by ARMR today215
not blocked26,216
Exploited478
Working exploit published566
Proof of concept only2,768
Forecast only97
No public exploit22,522
202330,949
Protected by Waratek161
Mitigation candidate40
No exploit published882
Outside Waratek scope205
Not applicable27,528
Withdrawn CVE2,133
Critical5,031
High11,637
Medium11,824
Low323
Unknown2,134
blocked by ARMR today161
not blocked30,786
not established2
Exploited567
Working exploit published557
Proof of concept only5,592
Forecast only110
No public exploit24,123
202440,704
Protected by Waratek108
Mitigation candidate28
No exploit published620
Outside Waratek scope186
Not applicable39,011
Withdrawn CVE751
Critical4,874
High15,332
Medium18,998
Low740
None1
Unknown759
blocked by ARMR today106
partly blocked2
not blocked40,596
Exploited747
Working exploit published403
Proof of concept only7,467
Forecast only83
No public exploit32,004
202549,972
Protected by Waratek103
Rule in development4
Mitigation candidate25
No exploit published731
Outside Waratek scope139
Not applicable47,148
Withdrawn CVE1,822
Critical4,490
High16,670
Medium23,043
Low3,040
None10
Unknown2,719
blocked by ARMR today103
not blocked49,867
not established2
Exploited727
Working exploit published594
Proof of concept only10,991
Forecast only17
No public exploit37,643
2026103,204
Protected by Waratek318
Mitigation candidate31
No exploit published5,951
Outside Waratek scope180
Not applicable93,937
Withdrawn CVE2,787
Critical11,258
High41,872
Medium37,380
Low6,665
None68
Unknown5,961
blocked by ARMR today314
partly blocked4
not blocked102,885
not established1
Exploited976
Working exploit published478
Proof of concept only19,685
Forecast only5
No public exploit82,060
19961999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-99320 | Unknown | 2026-11-19 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ipv6: raw: fix use-after-free in rawv6_send_hdrinc() rawv6_send_hdrinc() caches the route before handing the skb to l3mdev_ip6_out(). The VRF output path may replace skb->dst and release the original route, leaving the cached pointer stale. The function later dereferences that pointer for statistics accounting and as the output device passed to NF_HOOK(). Its RCU read-side critical section starts after l3mdev_ip6_out(), so it cannot prevent the old route from being reclaimed in between. Reload the route from the current skb destination after l3mdev_ip6_out() returns. KASAN reports a slab-use-after-free in rawv6_sendmsg(), with the route allocated by ip6_dst_alloc(), freed by dst_destroy() from rcu_core(), and the related RCU callback queued from vrf_l3_out(). |
| CVE-2026-92613 | Low | 2026-11-19 | Not applicable | No public exploit | In Eclipse iceoryx-rs, versions 0.0.11 to 0.0.13 and 0.1.0 as well as on the latest main branch. `SampleReceiver::<T>::take()` and `Sample::<T>::deref()` are safe functions that hand the caller a `&T` pointing at a chunk written by another iceoryx process, but the subscriber path neither requires `T: ShmSend` nor verifies that the received chunk is at least `size_of::<T>()` bytes / `align_of::<T>()`-aligned. A peer process that publishes an undersized chunk, or any chunk at all when the subscriber chose a pointer-bearing `T`, drives a `#![forbid(unsafe_code)]` subscriber into out-of-bounds reads of adjacent shared-memory chunks or dereference of a publisher-controlled pointer. Resolution: It will not be fixed since this is a known limitation in iceoryx as it is the users responsibility to specify the same data type on sender and receiver side. [iceoryx2](https://github.com/eclipse-iceoryx/iceoryx2) is the successor of iceoryx-rs where the API is designed to prevent this by default. It is strongly recommended to migrate to iceoryx2 which is actively maintained and receives security support. The iceoryx-rs package has officially reached End-of-life and will not receive any features, bugfixes or security fixes. |
| 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-85776 | High | 2026-11-19 | Not applicable | No public exploit | The WP Duplicate – WordPress Migration Plugin plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.1.11. This is due to a missing capability check and missing nonce check on the start_zip_creation, start_zip_download, local_sync_get_init_root_files, and local_sync_get_files_by_key AJAX actions in the start_zip_creation_dev() and sibling functions. This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite the plugin's prod_site_url setting so it points at an attacker-controlled host and enumerate arbitrary server directories, which when combined with a subsequent administrator-triggered sync results in an unsigned attacker-supplied ZIP archive being fetched, extracted via a WordPress-independent bridge deployed under the web root, resulting in remote code execution on the affected site. |
| 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-84998 | High | 2026-11-19 | Not applicable | No public exploit | The NextScripts: Social Networks Auto-Poster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'comment_author' and 'comment_agent' Comment Fields in all versions up to, and including, 4.4.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload executes in an administrator's browser session when the administrator views the WordPress comment moderation queue, including pending and unapproved comments, meaning no prior approval of the comment is required for exploitation. |
| CVE-2026-82950 | High | 2026-11-19 | Not applicable | No public exploit | The device only supports Wi-Fi protocols vulnerable to deauthentication attacks (WEP/WPA/WPA2). Should any event which would typically be logged to the user’s mobile device (such as arming or disarming the alarm or any tamper events) be incurred whilst the device is temporarily disconnected from its Wi-Fi network (such as via a deauthentication attack), those alerts will not be sent even after connection is regained. |
| CVE-2026-82949 | High | 2026-11-19 | Not applicable | No public exploit | The static codes used for information transmission throughout the 433.92 MHz system of the Guardian 2 system allow an attacker in proximity to monitor the movements of users inside the premises where the sensors are set up. This is further aided by the fact that codes transmitted reveal sensor type, although sensor location cannot be inferred from this traffic alone. |
| CVE-2026-82948 | High | 2026-11-19 | Not applicable | No public exploit | The Guardian 2 alarm unit lacks a mechanism to authenticate control commands sent over 433.92 MHz, which allows an attacker to replay the static commands to impersonate activity. The attacker can also disarm or arm the system at will if a Nexsmart keypad (product link) is in use, thus compromising the functionality of the alarm system completely. |
| 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-22311 | High | 2026-11-19 | Not applicable | No public exploit | The failed-login limiter of the JTL-Wawi synchronisation interface of JTL-Shop derives the client identity from the client-controlled X-Forwarded-For header and counts requests without credentials as failed logins. An unauthenticated remote attacker can block the synchronisation between JTL-Shop and JTL-Wawi with a few requests and repeat this indefinitely, so that orders are no longer handed over to JTL-Wawi. No data is disclosed and no code is executed. |
| 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-19609 | High | 2026-11-19 | Not applicable | No public exploit | Cross-site scripting in the embedded co-browsing feature in Unblu inc. Unblu Spark 7.0 through 7.57.9 and 8.0 before 8.40.2, on on-premises and cloud deployments, allows an unauthenticated remote attacker in the visitor role to execute arbitrary JavaScript in the browser of an agent taking part in the attacker's co-browsing session, via manipulated synchronized page attributes of the co-browsed page. The JavaScript runs in the context and under the identity of the agent's session in the Agent Desk or the Single Conversation Desk. Exploitation requires an agent to join an embedded co-browsing session with the attacker. Mobile co-apping isn't affected. |
| CVE-2026-14492 | Critical | 2026-11-19 | Not applicable | No public exploit | The WP Duplicate – WordPress Migration Plugin plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.1.11 via the save_single_batch_file function. This is due to a PHP type-juggling authentication bypass via loose != comparison with no is_string() guard, combined with unsanitized base64-decoded path construction in save_single_batch_file() lacking any directory traversal containment. This makes it possible for authenticated attackers, with custom-level access and above, to execute code on the server. Exploitation requires that the site owner has completed the plugin's initial setup so that the site_type and prod_key_random_id options are non-empty, though any non-empty secret value is bypassable via the type-juggling flaw. |
| CVE-2026-14491 | High | 2026-11-19 | Not applicable | No public exploit | The WP Duplicate – WordPress Migration Plugin plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.1.11 via the 'file_name' parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. The authentication bypass requires submitting the JSON boolean `true` as the `prod_key_random_id` value, which coerces against any non-empty stored secret so that the loose `!=` comparison evaluates to false, skipping the rejection branch entirely without knowledge of the secret. |
| CVE-2026-133117 | High | 2026-11-19 | Not applicable | No public exploit | WebToffee Product Feed before 2.4.4 for WordPress contains a use of hard-coded cryptographic key vulnerability that allows unauthenticated attackers to bypass the URL-cron signature check by computing a valid hash using the publicly known constant salt embedded in the plugin source. Attackers can send forged GET requests with attacker-controlled parameters to the unauthenticated init-hooked endpoint to repeatedly trigger product-feed generation, causing CPU/database resource exhaustion and overwriting of the generated feed file. |
| CVE-2026-133109 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via user and job names |
| CVE-2026-133108 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2 the current request details debug endpoint exposed authentication headers and session cookies |
| CVE-2026-133107 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via commit messages |
| 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-133097 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 agent Push authorization keys were predictable |
| CVE-2026-133096 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed queuing builds with personal changes of other users |
| CVE-2026-133095 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 a CSRF attack was possible on the Hub integration settings |
| CVE-2026-133094 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2 missing authorization allowed project developers to read arbitrary HashiCorp Vault secrets |
| CVE-2026-133093 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 code injection in parent project Kotlin DSL was possible via subproject settings |
| CVE-2026-133092 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git submodule URLs |
| CVE-2026-133091 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Users page was possible |
| CVE-2026-133090 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed overwriting versioned settings of other projects |
| CVE-2026-133089 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 the TFS helper process exposed an unauthenticated command server |
| CVE-2026-133088 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via FreeMarker notification templates |
| CVE-2026-133087 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a time zone callback in the Kotlin DSL sandbox |
| CVE-2026-133086 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a URL stream handler in the Kotlin DSL sandbox |
| CVE-2026-133085 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 an XXE was possible in the TFS helper process |
| CVE-2026-133084 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 vCS root credentials could be exposed via change viewer links |
| CVE-2026-133083 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in Server Health reports was possible |
| CVE-2026-133082 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 a DoS attack was possible via unauthenticated multipart requests |
| CVE-2026-133081 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git VCS root URLs |
| CVE-2026-133080 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven repository settings |
| CVE-2026-133079 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven dependencies of Kotlin DSL settings |
| CVE-2026-133078 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the Kotlin DSL sandbox |
| CVE-2026-133077 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 privilege escalation to system administrator was possible via Project Import |
| CVE-2026-133076 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via local repository URLs in Subversion VCS roots |
| CVE-2026-133057 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 the TFS helper server was exposed on all network interfaces |
| CVE-2026-133056 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in implicit agent requirements was possible |
| CVE-2026-133055 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the Failure Conditions page 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-133027 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 privilege escalation was possible via username handling in token authentication |
| CVE-2026-133026 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 code injection in generated Kotlin DSL was possible via matrix build parameters |
| CVE-2026-133025 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 missing authorization allowed project viewers to download project settings |
| CVE-2026-133024 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via personal builds with versioned settings |
| CVE-2026-133023 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Kotlin DSL compiler arguments |
| CVE-2026-133022 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1 remote code execution was possible via the Notification Rules form |
| CVE-2026-133021 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Mercurial subrepository paths |
| CVE-2026-133020 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.5 untrusted build approval for GitHub fork pull requests could be bypassed |
| CVE-2026-133019 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a context parameters callback in the Kotlin DSL sandbox |
| CVE-2026-133018 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a UI patches callback in the Kotlin DSL sandbox |
| CVE-2026-133017 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Git VCS root settings |
| CVE-2026-133016 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via script definitions in the Kotlin DSL settings repository |
| CVE-2026-133015 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via boot classpath libraries in the Kotlin DSL sandbox |
| CVE-2026-133014 | High | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via public reflection in the Kotlin DSL sandbox |
| 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-132996 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users |
| CVE-2026-132995 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 stored XSS on the build step settings page was possible |
| CVE-2026-132994 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI |
| CVE-2026-132993 | Low | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the notification rules editor was possible |
| CVE-2026-132992 | Low | 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 info popup was possible |
| 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 |