Overview 103,273 matches · 4,046 in Waratek scope · 244 protected · 579 exploited · 102 CISA KEV · 1,375 public PoC · 173 EPSS ≥ 0.5
103,273matches
4,046in Waratek scope3.9%
244protected0.2%
579exploited0.6%
102CISA KEV0.1%
1,375public PoC1.3%
173EPSS ≥ 0.50.2%
Protected by Waratek
245
0.2%
Rule in development
2
0.0%
Mitigation candidate
42
0.0%
No exploit published
3,757
3.6%
Outside Waratek scope
529
0.5%
Not applicable
98,698
95.6%
Withdrawn CVE
0
0.0%
blocked by ARMR today
244
0.2%
partly blocked
1
0.0%
not blocked
103,028
99.8%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 12,187 / quarter
Q4 212,059
Protected by Waratek16
Mitigation candidate4
No exploit published47
Outside Waratek scope36
Not applicable1,956
Medium2,059
blocked by ARMR today16
not blocked2,043
Exploited17
Working exploit published42
Proof of concept only32
Forecast only9
No public exploit1,959
Q1 222,480
Protected by Waratek27
Mitigation candidate1
No exploit published165
Outside Waratek scope15
Not applicable2,272
Medium2,480
blocked by ARMR today27
not blocked2,453
Exploited21
Working exploit published98
Proof of concept only68
Forecast only12
No public exploit2,281
Q2 222,387
Protected by Waratek12
Mitigation candidate1
No exploit published167
Outside Waratek scope39
Not applicable2,168
Medium2,387
blocked by ARMR today12
not blocked2,375
Exploited19
Working exploit published63
Proof of concept only133
Forecast only9
No public exploit2,163
Q3 222,470
Protected by Waratek14
No exploit published131
Outside Waratek scope34
Not applicable2,291
Medium2,470
blocked by ARMR today14
not blocked2,456
Exploited14
Working exploit published54
Proof of concept only163
Forecast only11
No public exploit2,228
Q4 222,571
Protected by Waratek5
Mitigation candidate1
No exploit published112
Outside Waratek scope25
Not applicable2,428
Medium2,571
blocked by ARMR today5
not blocked2,566
Exploited19
Working exploit published55
Proof of concept only589
Forecast only2
No public exploit1,906
Q1 232,797
Protected by Waratek5
No exploit published78
Outside Waratek scope24
Not applicable2,690
Medium2,797
blocked by ARMR today5
not blocked2,792
Exploited33
Working exploit published60
Proof of concept only772
Forecast only12
No public exploit1,920
Q2 233,111
Protected by Waratek9
Mitigation candidate5
No exploit published151
Outside Waratek scope25
Not applicable2,921
Medium3,111
blocked by ARMR today9
not blocked3,102
Exploited21
Working exploit published75
Proof of concept only602
Forecast only9
No public exploit2,404
Q3 232,833
Protected by Waratek9
Mitigation candidate2
No exploit published103
Outside Waratek scope24
Not applicable2,695
Medium2,833
blocked by ARMR today9
not blocked2,824
Exploited26
Working exploit published72
Proof of concept only671
Forecast only5
No public exploit2,059
Q4 233,083
Protected by Waratek6
Mitigation candidate3
No exploit published109
Outside Waratek scope23
Not applicable2,942
Medium3,083
blocked by ARMR today6
not blocked3,077
Exploited19
Working exploit published30
Proof of concept only362
No public exploit2,672
Q1 243,792
Protected by Waratek11
Mitigation candidate3
No exploit published116
Outside Waratek scope23
Not applicable3,639
Medium3,792
blocked by ARMR today11
not blocked3,781
Exploited21
Working exploit published34
Proof of concept only737
Forecast only4
No public exploit2,996
Q2 245,688
Protected by Waratek2
No exploit published96
Outside Waratek scope23
Not applicable5,567
Medium5,688
blocked by ARMR today2
not blocked5,686
Exploited33
Working exploit published28
Proof of concept only809
Forecast only5
No public exploit4,813
Q3 244,016
Protected by Waratek2
Mitigation candidate2
No exploit published54
Outside Waratek scope14
Not applicable3,944
Medium4,016
blocked by ARMR today2
not blocked4,014
Exploited25
Working exploit published31
Proof of concept only1,015
Forecast only1
No public exploit2,944
Q4 245,502
Protected by Waratek4
No exploit published56
Outside Waratek scope50
Not applicable5,392
Medium5,502
blocked by ARMR today4
not blocked5,498
Exploited50
Working exploit published21
Proof of concept only1,036
No public exploit4,395
Q1 256,190
Protected by Waratek6
Mitigation candidate3
No exploit published91
Outside Waratek scope9
Not applicable6,081
Medium6,190
blocked by ARMR today6
not blocked6,184
Exploited32
Working exploit published67
Proof of concept only1,363
Forecast only1
No public exploit4,727
Q2 256,106
Protected by Waratek10
Mitigation candidate5
No exploit published83
Outside Waratek scope14
Not applicable5,994
Medium6,106
blocked by ARMR today10
not blocked6,096
Exploited40
Working exploit published36
Proof of concept only1,718
Forecast only4
No public exploit4,308
Q3 255,277
Protected by Waratek10
Rule in development1
Mitigation candidate3
No exploit published173
Outside Waratek scope20
Not applicable5,070
Medium5,277
blocked by ARMR today10
not blocked5,267
Exploited31
Working exploit published39
Proof of concept only1,130
No public exploit4,077
Q4 255,470
Protected by Waratek11
Rule in development1
Mitigation candidate3
No exploit published126
Outside Waratek scope35
Not applicable5,294
Medium5,470
blocked by ARMR today11
not blocked5,459
Exploited30
Working exploit published28
Proof of concept only1,031
No public exploit4,381
Q1 266,183
Protected by Waratek9
Mitigation candidate1
No exploit published67
Outside Waratek scope37
Not applicable6,069
Medium6,183
blocked by ARMR today9
not blocked6,174
Exploited25
Working exploit published39
Proof of concept only1,419
No public exploit4,700
Q2 268,222
Protected by Waratek23
Mitigation candidate3
No exploit published242
Outside Waratek scope31
Not applicable7,923
Medium8,222
blocked by ARMR today23
not blocked8,199
Exploited29
Working exploit published36
Proof of concept only1,681
No public exploit6,476
Q3 2612,187
Protected by Waratek33
Mitigation candidate2
No exploit published744
Outside Waratek scope24
Not applicable11,384
Medium12,187
blocked by ARMR today32
partly blocked1
not blocked12,154
Exploited27
Working exploit published30
Proof of concept only2,212
No public exploit9,918
Q4 2610,849
Protected by Waratek21
No exploit published846
Outside Waratek scope4
Not applicable9,978
Medium10,849
blocked by ARMR today21
not blocked10,828
Exploited47
Working exploit published19
Proof of concept only1,583
No public exploit9,200
Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| 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 |