Search Results (112624 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-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-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-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-133086 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 a URL stream handler in the Kotlin DSL sandbox
CVE-2026-133089 1 Jetbrains 1 Teamcity 2026-11-20 8.1 High
In JetBrains TeamCity before 2026.2.2, 2026.1.6 the TFS helper process exposed an unauthenticated command server
CVE-2026-133092 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 Git submodule URLs
CVE-2026-128997 2 Romancode, Wordpress-extensions 2 Mapsvg, Mapsvg 2026-11-20 7.5 High
Missing Authorization vulnerability in RomanCode MapSVG mapsvg-lite-interactive-vector-maps allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MapSVG: from n/a through 9.0.5.
CVE-2026-133253 1 Jetbrains 1 Intellij Idea 2026-11-20 7.4 High
In JetBrains IntelliJ IDEA before 2026.3 untrusted projects could read files of other open projects via the built-in web server
CVE-2026-133246 1 Modified-shop 2 Modified-shop, Modified Ecommerce Shopsoftware 2026-11-20 7.2 High
modified eCommerce Shopsoftware through 3.3.0 contains a local file inclusion vulnerability that allows administrators to include arbitrary server files by storing ../ sequences in the content manager file name. Unauthenticated requests to shop_content.php then pass the stored path to include(), executing embedded PHP in uploaded content files or images as the web server user.
CVE-2026-22310 2026-11-20 8 High
When the setting for saving requests to non-existent pages (404) is enabled, JTL-Shop stores the raw requested URL in its redirect table, and the administration backend renders it without output encoding in the form used to edit a redirect. An unauthenticated remote attacker can store script code with a single request, which is executed in the browser session of an administrator who opens the affected redirect, allowing actions to be performed with the administrator's privileges. The setting is disabled by default in new installations but may still be enabled in older ones.
CVE-2026-99773 1 Linux 2 Linux, Linux Kernel 2026-11-20 7.0 High
In the Linux kernel, the following vulnerability has been resolved: drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind In [1], sashiko reported the following issue: === snip === Looking at how these fences are managed, drm_crtc_create_fence() creates a dma_fence without taking a reference to the drm_device or drm_crtc. Because the sync_file framework exposes this fence to userspace, the fence can outlive the CRTC. The dma_fence contract requires that data accessed by dma_fence_ops (like get_driver_name) must remain valid for an RCU grace period after the fence is signaled. However, drm_crtc_cleanup() and the subsequent freeing of the device do not wait for an RCU grace period via synchronize_rcu(). If userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device hot-unplug: CPU1 (Userspace) sync_file_get_name() ops = rcu_dereference(fence->ops); if (!dma_fence_test_signaled_flag()) // Preempted or delayed here CPU2 (Driver Teardown) Signals the fence (setting fence->ops = NULL) Destroys and frees the CRTC without waiting for an RCU grace period CPU1 (Resumes) ops->get_driver_name(fence) -> drm_crtc_fence_get_driver_name() crtc = fence_to_crtc(fence); // Casts to the freed CRTC return crtc->dev->driver->name; // Use-after-free ... Does the CRTC or DRM device need to be kept alive for the RCU grace period, or should the fence hold a proper reference to prevent the use-after-free when get_driver_name() and get_timeline_name() access the freed CRTC structure? === snap === I believe this to be a correct observation and this patch implements the suggestion of waiting for an RCU grace period before proceeding with destruction of the drm_crtc, so that get_driver_name() and get_timeline_name() can still work.