Overview 329,643 matches · 16,153 in Waratek scope · 1,368 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
329,643matches
16,153in Waratek scope4.9%
1,368protected0.4%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
1,370
0.4%
Rule in development
0
0.0%
Mitigation candidate
8
0.0%
No exploit published
14,775
4.5%
Outside Waratek scope
3,167
1.0%
Not applicable
291,534
88.4%
Withdrawn CVE
18,789
5.7%
Critical
33,544
10.2%
High
127,265
38.6%
Medium
135,730
41.2%
Low
10,310
3.1%
None
71
0.0%
Unknown
22,723
6.9%
blocked by ARMR today
1,368
0.4%
partly blocked
2
0.0%
not blocked
328,273
99.6%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
329,643
100.0%
split by
peak 82,026 / year
2007896
Protected by Waratek1
No exploit published32
Outside Waratek scope21
Not applicable808
Withdrawn CVE34
Critical2
High367
Medium439
Low54
Unknown34
blocked by ARMR today1
not blocked895
No public exploit896
20083,091
Protected by Waratek2
No exploit published134
Outside Waratek scope47
Not applicable2,881
Withdrawn CVE27
Critical13
High1,311
Medium1,585
Low155
Unknown27
blocked by ARMR today2
not blocked3,089
No public exploit3,091
20093,109
Protected by Waratek5
No exploit published195
Outside Waratek scope38
Not applicable2,831
Withdrawn CVE40
Critical8
High1,256
Medium1,642
Low163
Unknown40
blocked by ARMR today5
not blocked3,104
No public exploit3,109
20103,271
Protected by Waratek4
No exploit published167
Outside Waratek scope64
Not applicable3,010
Withdrawn CVE26
Critical16
High1,304
Medium1,677
Low248
Unknown26
blocked by ARMR today4
not blocked3,267
No public exploit3,271
20113,422
Protected by Waratek3
No exploit published205
Outside Waratek scope79
Not applicable3,116
Withdrawn CVE19
High1,363
Medium1,794
Low246
Unknown19
blocked by ARMR today3
not blocked3,419
No public exploit3,422
20124,408
Protected by Waratek6
No exploit published291
Outside Waratek scope65
Not applicable3,988
Withdrawn CVE58
Critical11
High1,369
Medium2,496
Low474
Unknown58
blocked by ARMR today6
not blocked4,402
No public exploit4,408
20134,683
Protected by Waratek16
Mitigation candidate1
No exploit published316
Outside Waratek scope263
Not applicable3,970
Withdrawn CVE117
Critical13
High1,415
Medium2,647
Low491
Unknown117
blocked by ARMR today16
not blocked4,667
No public exploit4,683
20147,087
Protected by Waratek32
No exploit published292
Outside Waratek scope233
Not applicable6,461
Withdrawn CVE69
Critical9
High1,526
Medium4,856
Low627
Unknown69
blocked by ARMR today32
not blocked7,055
No public exploit7,087
20155,817
Protected by Waratek26
No exploit published307
Outside Waratek scope164
Not applicable5,224
Withdrawn CVE96
Critical32
High1,928
Medium3,208
Low553
Unknown96
blocked by ARMR today26
not blocked5,791
No public exploit5,817
20165,926
Protected by Waratek40
No exploit published478
Outside Waratek scope108
Not applicable5,236
Withdrawn CVE64
Critical795
High2,559
Medium2,293
Low215
Unknown64
blocked by ARMR today40
not blocked5,886
No public exploit5,926
201716,567
Protected by Waratek81
No exploit published700
Outside Waratek scope208
Not applicable12,118
Withdrawn CVE3,460
Critical1,707
High5,857
Medium5,314
Low229
Unknown3,460
blocked by ARMR today80
partly blocked1
not blocked16,486
No public exploit16,567
201816,728
Protected by Waratek159
No exploit published724
Outside Waratek scope195
Not applicable14,012
Withdrawn CVE1,638
Critical2,236
High6,959
Medium5,743
Low152
Unknown1,638
blocked by ARMR today159
not blocked16,569
No public exploit16,728
201917,648
Protected by Waratek94
No exploit published795
Outside Waratek scope247
Not applicable14,883
Withdrawn CVE1,629
Critical2,331
High6,650
Medium6,735
Low303
Unknown1,629
blocked by ARMR today94
not blocked17,554
No public exploit17,648
202018,054
Protected by Waratek127
Mitigation candidate1
No exploit published928
Outside Waratek scope239
Not applicable15,864
Withdrawn CVE895
Critical2,441
High7,264
Medium7,057
Low397
Unknown895
blocked by ARMR today127
not blocked17,927
No public exploit18,054
202120,628
Protected by Waratek95
No exploit published642
Outside Waratek scope321
Not applicable17,770
Withdrawn CVE1,800
Critical2,502
High8,263
Medium7,676
Low387
Unknown1,800
blocked by ARMR today95
not blocked20,533
No public exploit20,628
202222,520
Protected by Waratek168
Mitigation candidate1
No exploit published836
Outside Waratek scope246
Not applicable19,921
Withdrawn CVE1,348
Critical3,458
High8,766
Medium8,578
Low368
Unknown1,350
blocked by ARMR today168
not blocked22,352
No public exploit22,520
202324,122
Protected by Waratek113
Mitigation candidate1
No exploit published732
Outside Waratek scope174
Not applicable20,977
Withdrawn CVE2,125
Critical3,412
High9,248
Medium9,055
Low281
Unknown2,126
blocked by ARMR today113
not blocked24,009
No public exploit24,122
202432,004
Protected by Waratek72
No exploit published558
Outside Waratek scope170
Not applicable30,457
Withdrawn CVE747
Critical3,092
High12,383
Medium15,148
Low627
None1
Unknown753
blocked by ARMR today72
not blocked31,932
No public exploit32,004
202537,636
Protected by Waratek68
No exploit published653
Outside Waratek scope121
Not applicable34,979
Withdrawn CVE1,815
Critical2,917
High13,478
Medium17,493
Low1,026
None10
Unknown2,712
blocked by ARMR today68
not blocked37,568
No public exploit37,636
202682,026
Protected by Waratek258
Mitigation candidate4
No exploit published5,790
Outside Waratek scope164
Not applicable73,028
Withdrawn CVE2,782
Critical8,549
High33,999
Medium30,294
Low3,314
None60
Unknown5,810
blocked by ARMR today257
partly blocked1
not blocked81,768
No public exploit82,026
2008201020122014201620182020202220242026
| 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-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-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 |