WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Published from 2021-10-01✕
Overview 203,776 matches · 9,392 in Waratek scope · 709 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
203,776matches 9,392in Waratek scope4.6% 709protected0.3% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
split by peak 30,755 / quarter
Withdrawn CVE: 9,431Not applicable: 183,998Outside Waratek scope: 955No exploit published: 8,676Mitigation candidate: 6Protected by Waratek: 710 Unknown: 13,365None: 71Low: 5,701Medium: 82,527High: 79,949Critical: 22,163 not blocked: 203,066partly blocked: 1blocked by ARMR today: 709 No public exploit: 203,776
Q4 215,468 Protected by Waratek31 No exploit published107 Outside Waratek scope80 Not applicable4,636 Withdrawn CVE614 Critical735 High2,075 Medium1,959 Low85 Unknown614 blocked by ARMR today31 not blocked5,437 No public exploit5,468 Q1 225,697 Protected by Waratek53 No exploit published242 Outside Waratek scope42 Not applicable5,061 Withdrawn CVE299 Critical869 High2,141 Medium2,281 Low107 Unknown299 blocked by ARMR today53 not blocked5,644 No public exploit5,697 Q2 225,701 Protected by Waratek35 No exploit published216 Outside Waratek scope81 Not applicable5,292 Withdrawn CVE77 Critical996 High2,398 Medium2,163 Low67 Unknown77 blocked by ARMR today35 not blocked5,666 No public exploit5,701 Q3 226,066 Protected by Waratek37 Mitigation candidate1 No exploit published210 Outside Waratek scope84 Not applicable5,330 Withdrawn CVE404 Critical918 High2,402 Medium2,228 Low114 Unknown404 blocked by ARMR today37 not blocked6,029 No public exploit6,066 Q4 225,056 Protected by Waratek43 No exploit published168 Outside Waratek scope39 Not applicable4,238 Withdrawn CVE568 Critical675 High1,825 Medium1,906 Low80 Unknown570 blocked by ARMR today43 not blocked5,013 No public exploit5,056 Q1 235,905 Protected by Waratek30 Mitigation candidate1 No exploit published152 Outside Waratek scope49 Not applicable4,827 Withdrawn CVE846 Critical892 High2,197 Medium1,920 Low50 Unknown846 blocked by ARMR today30 not blocked5,875 No public exploit5,905 Q2 235,687 Protected by Waratek28 No exploit published223 Outside Waratek scope39 Not applicable5,029 Withdrawn CVE368 Critical723 High2,119 Medium2,404 Low73 Unknown368 blocked by ARMR today28 not blocked5,659 No public exploit5,687 Q3 235,789 Protected by Waratek24 No exploit published161 Outside Waratek scope38 Not applicable4,792 Withdrawn CVE774 Critical750 High2,113 Medium2,059 Low93 Unknown774 blocked by ARMR today24 not blocked5,765 No public exploit5,789 Q4 236,741 Protected by Waratek31 No exploit published196 Outside Waratek scope48 Not applicable6,329 Withdrawn CVE137 Critical1,047 High2,819 Medium2,672 Low65 Unknown138 blocked by ARMR today31 not blocked6,710 No public exploit6,741 Q1 246,685 Protected by Waratek27 No exploit published180 Outside Waratek scope42 Not applicable6,214 Withdrawn CVE222 Critical854 High2,497 Medium2,996 Low113 Unknown225 blocked by ARMR today27 not blocked6,658 No public exploit6,685 Q2 249,837 Protected by Waratek12 No exploit published146 Outside Waratek scope36 Not applicable9,331 Withdrawn CVE312 Critical760 High3,761 Medium4,813 Low190 Unknown313 blocked by ARMR today12 not blocked9,825 No public exploit9,837 Q3 246,509 Protected by Waratek17 No exploit published105 Outside Waratek scope22 Not applicable6,230 Withdrawn CVE135 Critical653 High2,636 Medium2,944 Low141 Unknown135 blocked by ARMR today17 not blocked6,492 No public exploit6,509 Q4 248,973 Protected by Waratek16 No exploit published127 Outside Waratek scope70 Not applicable8,682 Withdrawn CVE78 Critical825 High3,489 Medium4,395 Low183 None1 Unknown80 blocked by ARMR today16 not blocked8,957 No public exploit8,973 Q1 259,686 Protected by Waratek12 No exploit published126 Outside Waratek scope15 Not applicable9,071 Withdrawn CVE462 Critical766 High3,528 Medium4,727 Low203 Unknown462 blocked by ARMR today12 not blocked9,674 No public exploit9,686 Q2 259,103 Protected by Waratek24 No exploit published129 Outside Waratek scope26 Not applicable8,414 Withdrawn CVE510 Critical770 High3,297 Medium4,308 Low212 None6 Unknown510 blocked by ARMR today24 not blocked9,079 No public exploit9,103 Q3 258,701 Protected by Waratek18 No exploit published223 Outside Waratek scope34 Not applicable7,945 Withdrawn CVE481 Critical715 High3,129 Medium4,077 Low298 None1 Unknown481 blocked by ARMR today18 not blocked8,683 No public exploit8,701 Q4 2510,146 Protected by Waratek14 No exploit published175 Outside Waratek scope46 Not applicable9,549 Withdrawn CVE362 Critical666 High3,524 Medium4,381 Low313 None3 Unknown1,259 blocked by ARMR today14 not blocked10,132 No public exploit10,146 Q1 2611,703 Protected by Waratek21 Mitigation candidate2 No exploit published142 Outside Waratek scope58 Not applicable10,379 Withdrawn CVE1,101 Critical1,110 High4,160 Medium4,700 Low503 None33 Unknown1,197 blocked by ARMR today21 not blocked11,682 No public exploit11,703 Q2 2615,274 Protected by Waratek74 Mitigation candidate1 No exploit published716 Outside Waratek scope44 Not applicable14,256 Withdrawn CVE183 Critical1,591 High6,380 Medium6,476 Low636 None8 Unknown183 blocked by ARMR today74 not blocked15,200 No public exploit15,274 Q3 2630,755 Protected by Waratek109 No exploit published3,133 Outside Waratek scope43 Not applicable26,711 Withdrawn CVE759 Critical3,747 High13,295 Medium9,918 Low1,075 None15 Unknown2,705 blocked by ARMR today108 partly blocked1 not blocked30,646 No public exploit30,755 Q4 2624,294 Protected by Waratek54 Mitigation candidate1 No exploit published1,799 Outside Waratek scope19 Not applicable21,682 Withdrawn CVE739 Critical2,101 High10,164 Medium9,200 Low1,100 None4 Unknown1,725 blocked by ARMR today54 not blocked24,240 No public exploit24,294
Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
203,776 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 1 of 2,038 next ›
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
‹ prev page 1 of 2,038 next ›