Overview 118,029 matches · 4,941 in Waratek scope · 297 protected · 682 exploited · 140 CISA KEV · 1,951 public PoC · 276 EPSS ≥ 0.5
118,029matches
4,941in Waratek scope4.2%
297protected0.3%
682exploited0.6%
140CISA KEV0.1%
1,951public PoC1.7%
276EPSS ≥ 0.50.2%
Protected by Waratek
298
0.3%
Rule in development
2
0.0%
Mitigation candidate
67
0.1%
No exploit published
4,574
3.9%
Outside Waratek scope
803
0.7%
Not applicable
112,284
95.1%
Withdrawn CVE
1
0.0%
blocked by ARMR today
297
0.3%
partly blocked
1
0.0%
not blocked
117,731
99.7%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 37,380 / year
20191,380
Protected by Waratek5
No exploit published46
Outside Waratek scope20
Not applicable1,309
Medium1,380
blocked by ARMR today5
not blocked1,375
Exploited6
Working exploit published43
Proof of concept only7
Forecast only1
No public exploit1,323
20207,359
Protected by Waratek35
Mitigation candidate17
No exploit published517
Outside Waratek scope131
Not applicable6,659
Medium7,359
blocked by ARMR today35
not blocked7,324
Exploited58
Working exploit published197
Proof of concept only37
Forecast only10
No public exploit7,057
20218,137
Protected by Waratek29
Mitigation candidate12
No exploit published301
Outside Waratek scope159
Not applicable7,636
Medium8,137
blocked by ARMR today29
not blocked8,108
Exploited86
Working exploit published240
Proof of concept only90
Forecast only44
No public exploit7,677
20229,908
Protected by Waratek58
Mitigation candidate3
No exploit published575
Outside Waratek scope113
Not applicable9,159
Medium9,908
blocked by ARMR today58
not blocked9,850
Exploited73
Working exploit published270
Proof of concept only953
Forecast only34
No public exploit8,578
202311,824
Protected by Waratek29
Mitigation candidate10
No exploit published441
Outside Waratek scope96
Not applicable11,248
Medium11,824
blocked by ARMR today29
not blocked11,795
Exploited97
Working exploit published237
Proof of concept only2,408
Forecast only26
No public exploit9,056
202418,998
Protected by Waratek19
Mitigation candidate5
No exploit published322
Outside Waratek scope110
Not applicable18,542
Medium18,998
blocked by ARMR today19
not blocked18,979
Exploited129
Working exploit published114
Proof of concept only3,597
Forecast only10
No public exploit15,148
202523,043
Protected by Waratek37
Rule in development2
Mitigation candidate14
No exploit published473
Outside Waratek scope78
Not applicable22,439
Medium23,043
blocked by ARMR today37
not blocked23,006
Exploited127
Working exploit published170
Proof of concept only5,244
Forecast only5
No public exploit17,497
202637,380
Protected by Waratek86
Mitigation candidate6
No exploit published1,899
Outside Waratek scope96
Not applicable35,292
Withdrawn CVE1
Medium37,380
blocked by ARMR today85
partly blocked1
not blocked37,294
Exploited106
Working exploit published124
Proof of concept only6,899
No public exploit30,251
20192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-132928 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in Perforce job details was possible |
| CVE-2026-132927 | Medium | 2026-11-19 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.2, 2026.1.4 the Perforce Administrator Access password could be written to the server log |