Export limit exceeded: 430281 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430281 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430281 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430281 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-133015 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8.8 High |
| 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-133027 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8.8 High |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 privilege escalation was possible via username handling in token authentication | ||||
| CVE-2026-133035 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2.1 stored XSS on the change Files tab was possible | ||||
| CVE-2026-133076 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.5 High |
| 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-133080 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8.8 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven repository settings | ||||
| CVE-2026-133081 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.5 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git VCS root URLs | ||||
| CVE-2026-133083 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in Server Health reports was possible | ||||
| CVE-2026-133084 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.7 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 vCS root credentials could be exposed via change viewer links | ||||
| CVE-2026-133254 | 1 Jetbrains | 1 Intellij Idea | 2026-11-20 | 8.3 High |
| In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 code execution was possible in untrusted projects via the Code Provenance plugin | ||||
| CVE-2026-133261 | 1 Jetbrains | 1 Youtrack | 2026-11-20 | 5.4 Medium |
| In JetBrains YouTrack before 2026.2.19840 an HTML injection in email notifications was possible via issue descriptions | ||||
| CVE-2026-133264 | 1 Jetbrains | 1 Youtrack | 2026-11-20 | 3.1 Low |
| In JetBrains YouTrack before 2026.2.19840 private issue summaries and descriptions could be read via agile board queries for archived projects | ||||
| CVE-2026-133274 | 1 Vanhauser-thc | 1 Thc-hydra | 2026-11-20 | 6.5 Medium |
| THC-Hydra through 9.7 contains a stack buffer overflow vulnerability in analyze_server_response() of hydra-http-form.c that allows malicious HTTP servers to corrupt memory via crafted Set-Cookie headers. Attackers can send a Set-Cookie header with an extra leading space followed by a repeated cookie name, causing a negative strncpy length that overflows tmpcookie and crashes Hydra. | ||||
| CVE-2026-133276 | 1 Pydantic | 1 Pydantic | 2026-11-20 | 5.3 Medium |
| When extra data is allowed (extra=Extra.allow), providing a __pydantic_initialised__ key when validating a Pydantic V1 dataclass makes it considered as already validated, resulting in field values not being validated. The __init__() method of Pydantic V1 dataclasses stores all the provided keyword arguments in the instance __dict__ before validation, so a __pydantic_initialised__ keyword argument overrides the internal flag used to skip validation of already validated instances. As a result, data returned by validation doesn't match the declared type. Affected are applications validating untrusted data into Pydantic V1 dataclasses allowing extra data. The issue was fixed in Pydantic 1.10.27. Users relying on the pydantic.v1 namespace in Pydantic V2 should upgrade to 2.14.2 or later. | ||||
| CVE-2026-47278 | 1 Frappe | 1 Frappe | 2026-11-20 | N/A |
| Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, the add_comment handler in frappe/templates/includes/comments/comments.py trusts the client-provided comment_by and comment_email fields. A caller can submit chosen identity metadata that is stored with a comment, causing the comment to appear to originate from another name or email address. This issue is fixed in versions 15.108.0 and 16.18.3. | ||||
| CVE-2026-128915 | 2 Instawp, Wordpress-extensions | 2 Instawp Connect, Instawp Connect | 2026-11-20 | 8.5 High |
| Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in InstaWP InstaWP Connect instawp-connect allows Blind SQL Injection.This issue affects InstaWP Connect: from n/a through 0.1.4.4. | ||||
| CVE-2026-116550 | 2 Smub, Wordpress-extensions | 2 Nextgen Gallery, Nextgen Gallery | 2026-11-20 | 7.2 High |
| The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.5.5 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. Exploitation requires the plugin's "What must the lightbox be applied to?" setting (thumbEffectContext) to be configured as "Try to apply to all images" or "Try to apply to all images that link to image files," which is not the shipping default, and also requires the attacker's comment to reach a publicly rendered state. | ||||
| CVE-2026-124217 | 3 Genetech Products, Genetechproducts, Wordpress-extensions | 4 Pie Register, Pie Register – User Registration, Profiles & Content Restriction, Pie Register – User Registration, Profiles & Content Restriction and 1 more | 2026-11-20 | 5.3 Medium |
| The Pie Register – User Registration, Profiles & Content Restriction plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.8.4.17 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the role of the site's primary administrator account (user ID 1) with the registration form's configured role, demoting the administrator to a lower-privileged role and locking them out of wp-admin. This vulnerability is exploitable only on PHP 8+, where casting a WP_Error object to int yields 1, causing the role modification to target user ID 1. | ||||
| CVE-2026-130964 | 1 Google | 1 Chrome | 2026-11-20 | 8.1 High |
| Confused deputy in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-130962 | 2 Apple, Google | 2 Iphone Os, Chrome | 2026-11-20 | 8.1 High |
| Incomplete cleanup in Navigation in Google Chrome on on iOS prior to 158.0.8127.36 allowed a remote attacker to potentially bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-130666 | 1 Imagemagick | 1 Imagemagick | 2026-11-20 | 5.3 Medium |
| ImageMagick before 7.1.2-35 contains a policy bypass vulnerability that allows attackers to evade resource limits because a policy check is missing when reading XMP profiles. Attackers can supply an image with a crafted XMP profile to trigger excessive memory usage and cause denial of service. | ||||