WaratekVRT Sign in
Reset
More filters (2)
Columns
Including CVEs outside Waratek scope✕Protection: None✕Published from 2021-02-01✕
Overview 270,243 matches · 9,816 in Waratek scope · 0 protected · 3,958 exploited · 1,054 CISA KEV · 5,962 public PoC · 1,663 EPSS ≥ 0.5
split by peak 37,591 / quarter
Withdrawn CVE: 10,223Not applicable: 248,941Outside Waratek scope: 1,263No exploit published: 9,648Mitigation candidate: 162Rule in development: 6 Unknown: 14,159None: 79Low: 11,515Medium: 108,509High: 103,556Critical: 32,425 not blocked: 270,243 No public exploit: 216,324Forecast only: 451Proof of concept only: 46,521Working exploit published: 2,989Exploited: 3,958
Q1 213,061 Mitigation candidate3 No exploit published87 Outside Waratek scope39 Not applicable2,755 Withdrawn CVE177 Critical436 High1,241 Medium1,143 Low64 Unknown177 not blocked3,061 Exploited78 Working exploit published78 Proof of concept only42 Forecast only34 No public exploit2,829 Q2 215,346 Rule in development1 Mitigation candidate6 No exploit published229 Outside Waratek scope110 Not applicable4,628 Withdrawn CVE372 Critical646 High2,207 Medium2,012 Low109 Unknown372 not blocked5,346 Exploited135 Working exploit published130 Proof of concept only43 Forecast only42 No public exploit4,996 Q3 215,760 Mitigation candidate8 No exploit published139 Outside Waratek scope53 Not applicable5,350 Withdrawn CVE210 Critical707 High2,405 Medium2,326 Low112 Unknown210 not blocked5,760 Exploited130 Working exploit published108 Proof of concept only45 Forecast only44 No public exploit5,433 Q4 215,726 Mitigation candidate6 No exploit published108 Outside Waratek scope82 Not applicable4,915 Withdrawn CVE615 Critical810 High2,174 Medium2,043 Low84 Unknown615 not blocked5,726 Exploited103 Working exploit published94 Proof of concept only63 Forecast only29 No public exploit5,437 Q1 226,250 Mitigation candidate4 No exploit published250 Outside Waratek scope45 Not applicable5,651 Withdrawn CVE300 Critical995 High2,395 Medium2,453 Low107 Unknown300 not blocked6,250 Exploited141 Working exploit published184 Proof of concept only258 Forecast only23 No public exploit5,644 Q2 226,379 Rule in development1 Mitigation candidate7 No exploit published226 Outside Waratek scope82 Not applicable5,980 Withdrawn CVE83 Critical1,161 High2,689 Medium2,375 Low71 Unknown83 not blocked6,379 Exploited126 Working exploit published160 Proof of concept only407 Forecast only20 No public exploit5,666 Q3 226,841 Mitigation candidate6 No exploit published229 Outside Waratek scope90 Not applicable6,111 Withdrawn CVE405 Critical1,169 High2,692 Medium2,456 Low119 Unknown405 not blocked6,841 Exploited100 Working exploit published117 Proof of concept only565 Forecast only30 No public exploit6,029 Q4 226,746 Mitigation candidate3 No exploit published196 Outside Waratek scope52 Not applicable5,925 Withdrawn CVE570 Critical1,042 High2,484 Medium2,566 Low82 Unknown572 not blocked6,746 Exploited98 Working exploit published100 Proof of concept only1,516 Forecast only19 No public exploit5,013 Q1 237,781 Mitigation candidate2 No exploit published165 Outside Waratek scope58 Not applicable6,709 Withdrawn CVE847 Critical1,308 High2,775 Medium2,792 Low59 Unknown847 not blocked7,781 Exploited137 Working exploit published134 Proof of concept only1,596 Forecast only39 No public exploit5,875 Q2 237,459 Mitigation candidate15 No exploit published296 Outside Waratek scope46 Not applicable6,732 Withdrawn CVE370 Critical1,117 High2,785 Medium3,102 Low85 Unknown370 not blocked7,459 Exploited139 Working exploit published191 Proof of concept only1,445 Forecast only25 No public exploit5,659 Q3 237,670 Mitigation candidate8 No exploit published187 Outside Waratek scope48 Not applicable6,648 Withdrawn CVE779 Critical1,199 High2,764 Medium2,824 Low104 Unknown779 not blocked7,670 Exploited148 Working exploit published149 Proof of concept only1,593 Forecast only15 No public exploit5,765 Q4 237,876 Mitigation candidate13 No exploit published234 Outside Waratek scope53 Not applicable7,439 Withdrawn CVE137 Critical1,350 High3,242 Medium3,077 Low69 Unknown138 not blocked7,876 Exploited133 Working exploit published81 Proof of concept only924 Forecast only28 No public exploit6,710 Q1 248,870 Mitigation candidate13 No exploit published202 Outside Waratek scope49 Not applicable8,382 Withdrawn CVE224 Critical1,407 High3,317 Medium3,781 Low138 Unknown227 not blocked8,870 Exploited179 Working exploit published99 Proof of concept only1,920 Forecast only14 No public exploit6,658 Q2 2411,990 Mitigation candidate4 No exploit published165 Outside Waratek scope41 Not applicable11,467 Withdrawn CVE313 Critical1,212 High4,542 Medium5,686 Low235 Unknown315 not blocked11,990 Exploited208 Working exploit published100 Proof of concept only1,804 Forecast only53 No public exploit9,825 Q3 248,634 Mitigation candidate6 No exploit published111 Outside Waratek scope24 Not applicable8,357 Withdrawn CVE136 Critical1,036 High3,288 Medium4,014 Low160 Unknown136 not blocked8,634 Exploited166 Working exploit published107 Proof of concept only1,861 Forecast only8 No public exploit6,492 Q4 2411,102 Mitigation candidate5 No exploit published142 Outside Waratek scope72 Not applicable10,805 Withdrawn CVE78 Critical1,182 High4,138 Medium5,498 Low203 None1 Unknown80 not blocked11,102 Exploited183 Working exploit published93 Proof of concept only1,862 Forecast only7 No public exploit8,957 Q1 2512,391 Mitigation candidate4 No exploit published151 Outside Waratek scope23 Not applicable11,747 Withdrawn CVE466 Critical1,144 High4,298 Medium6,184 Low299 Unknown466 not blocked12,391 Exploited168 Working exploit published138 Proof of concept only2,405 Forecast only6 No public exploit9,674 Q2 2512,173 Rule in development1 Mitigation candidate8 No exploit published153 Outside Waratek scope31 Not applicable11,470 Withdrawn CVE510 Critical1,082 High3,921 Medium6,096 Low558 None6 Unknown510 not blocked12,173 Exploited194 Working exploit published88 Proof of concept only2,803 Forecast only9 No public exploit9,079 Q3 2512,184 Rule in development1 Mitigation candidate6 No exploit published238 Outside Waratek scope39 Not applicable11,418 Withdrawn CVE482 Critical1,198 High3,987 Medium5,267 Low1,249 None1 Unknown482 not blocked12,184 Exploited191 Working exploit published294 Proof of concept only3,015 Forecast only1 No public exploit8,683 Q4 2513,119 Rule in development2 Mitigation candidate5 No exploit published189 Outside Waratek scope46 Not applicable12,513 Withdrawn CVE364 Critical1,030 High4,437 Medium5,459 Low929 None3 Unknown1,261 not blocked13,119 Exploited180 Working exploit published70 Proof of concept only2,737 No public exploit10,132 Q1 2616,221 Mitigation candidate8 No exploit published160 Outside Waratek scope62 Not applicable14,888 Withdrawn CVE1,103 Critical1,657 High5,949 Medium6,174 Low1,209 None33 Unknown1,199 not blocked16,221 Exploited199 Working exploit published134 Proof of concept only4,203 Forecast only3 No public exploit11,682 Q2 2620,777 Mitigation candidate10 No exploit published754 Outside Waratek scope49 Not applicable19,781 Withdrawn CVE183 Critical2,266 High8,490 Medium8,199 Low1,628 None11 Unknown183 not blocked20,777 Exploited248 Working exploit published147 Proof of concept only5,180 Forecast only2 No public exploit15,200 Q3 2637,591 Mitigation candidate11 No exploit published3,206 Outside Waratek scope47 Not applicable33,568 Withdrawn CVE759 Critical4,724 High15,784 Medium12,154 Low2,205 None19 Unknown2,705 not blocked37,591 Exploited307 Working exploit published145 Proof of concept only6,493 No public exploit30,646 Q4 2628,296 Mitigation candidate1 No exploit published1,831 Outside Waratek scope22 Not applicable25,702 Withdrawn CVE740 Critical2,547 High11,552 Medium10,828 Low1,637 None5 Unknown1,727 not blocked28,296 Exploited267 Working exploit published48 Proof of concept only3,741 No public exploit24,240
Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
270,243 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 1 of 2,703 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,703 next ›