Export limit exceeded: 429988 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429988 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429988 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429988 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| 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. | ||||
| CVE-2026-99775 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: xfrm: interface: validate the IP header on xmit Packets injected into an xfrm interface (e.g. AF_PACKET on an xfrmi device) reach the xfrm output path without IP header validation, but xfrm4_transport_output() uses iph->ihl for __skb_pull() and memmove() and expects the header to be valid. vti_tunnel_xmit() already calls pskb_inet_may_pull() before handing packets to the xfrm output path. Do the same in xfrmi_xmit() and perform the header checks ip_rcv_core()/ip6_rcv_core() do on entry to the IP stack: reject wrong IP versions and malformed IPv4 header lengths. | ||||
| CVE-2026-99790 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 5.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: NFSD: stop registering with rpcbind after a failure in listener_set nfsd_nl_listener_set_doit() calls svc_xprt_create_from_sa() once for each requested listener and passes flags of 0, so every listener registers with rpcbind on its own. A rpcbind that accepts the connection and never replies therefore costs one timeout for each entry. With the cap of 1024 entries the request can hold nfsd_mutex for about 34 minutes, which is roughly 17 times the hung-task threshold. One failure is enough to know that the next call will not fare better. Read svc_rpcb_failure_count() before the create loop, and pass SVC_SOCK_ANONYMOUS for the rest of the request once the count moves. | ||||
| CVE-2026-99791 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: xfs: improve dirent bounds checking in scrub and repair LOLLM complains that we don't do enough bounds checking of the directory entries in directory blocks when we're looking for errors or trying to salvage entries. Let's improve that with more detailed checks. | ||||
| CVE-2026-99793 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 5.0 Medium |
| In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Only accept connection responses to outstanding requests An outgoing channel waits in BT_CONNECT until security and the feature mask exchange complete, and only then sends its connection request. A peer can answer it before that with a connection response matching our source CID. The channel then moves to BT_CONFIG, completes configuration and becomes connected before security has completed. If security then fails, l2cap_security_cfm() leaves the connected channel alone, so it stays up on a link that did not reach the required security level. A connection response with a zero source CID is matched by identifier. Another channel can hold the same identifier for a response it still has to send, so the lookup can pick the wrong channel. Only accept a connection response while our request is outstanding, and only look at such channels when matching by identifier. | ||||
| CVE-2026-105074 | 2 Shortpixel, Wordpress-extensions | 2 Shortpixel Image Optimizer, Shortpixel Image Optimizer | 2026-11-20 | 7.1 High |
| Cross-Site Request Forgery (CSRF) vulnerability in ShortPixel ShortPixel Image Optimizer shortpixel-image-optimiser allows Cross Site Request Forgery.This issue affects ShortPixel Image Optimizer: from n/a through 6.6.1. | ||||
| CVE-2026-130953 | 1 Google | 1 Chrome | 2026-11-20 | 6.8 Medium |
| Incorrect authorization in Core in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-130940 | 1 Google | 1 Chrome | 2026-11-20 | 4.2 Medium |
| Improper state validation in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-131091 | 1 Google | 2 Android, Chrome | 2026-11-20 | 8.1 High |
| Missing authorization in Autofill in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-131014 | 1 Google | 2 Android, Chrome | 2026-11-20 | 7.4 High |
| Confused deputy in Grid in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker to bypass web origin policy via crafted network traffic. (Chromium security severity: Medium) | ||||
| CVE-2026-130990 | 1 Google | 1 Chrome | 2026-11-20 | 8.1 High |
| Missing authorization in PersistentCache in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted PDF file. (Chromium security severity: Medium) | ||||
| CVE-2026-130988 | 1 Google | 1 Chrome | 2026-11-20 | 4.3 Medium |
| Out of bounds read in V8 in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-130985 | 1 Google | 1 Chrome | 2026-11-20 | 6.5 Medium |
| Improper input validation in DOMStorage in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-123866 | 1 Nodejs | 1 Nodejs | 2026-11-20 | 7.5 High |
| A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer `RST_STREAM` or by the server's own per-stream timeout destroying the stream, the stream's response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. This vulnerability affects Node.js 26.x, 24.x, and 22.x. | ||||
| CVE-2026-119088 | 2 Joedolson, Wordpress-extensions | 2 My-calendar, My Calendar | 2026-11-20 | 6.4 Medium |
| The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'mc_template (template body); event_title (payload storage)' parameter in all versions up to, and including, 3.8.13 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. Successful exploitation requires the site to have granted mc_add_events to Subscriber-level users (a configurable plugin permission), and relies on a privileged user — such as an Administrator — following the event preview link surfaced on the My Calendar Events management screen. | ||||
| CVE-2026-130984 | 1 Google | 1 Chrome | 2026-11-20 | 8.1 High |
| Incorrect authorization in Canvas in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-133323 | 1 Mitel | 1 Micollab | 2026-11-20 | 10 Critical |
| A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an unauthenticated attacker to conduct a blind command injection attack due to insufficient parameter sanitization. A successful exploit could allow an attacker to execute arbitrary commands within the context of the system. This is MTLVULN-1864. | ||||
| CVE-2026-133476 | 1 Dolibarr | 2 Dolibarr Erp/crm, Dolibarr Erp\/crm | 2026-11-20 | 8.8 High |
| In Dolibarr before 24.0.3, dolForgeSQLCriteriaCallback() in htdocs/core/lib/functions.lib.php allows account takeover because it strips only a single table-name prefix from a Universal Search Filter (sqlfilters) operand before checking it against the forbidden-field denylist (pass, pass_crypted, api_key). MariaDB and MySQL accept a two-level qualification such as schema.alias.column, so an operand of the form dolibarr.u.pass_crypted survives the check and is emitted into the WHERE clause. A remote authenticated user holding only the holiday read and readall permissions, which confer no user-management or administrative access, can use the resulting boolean oracle at GET /api/index.php/holidays to recover any user's bcrypt password hash and api_key one character at a time, including an administrator's. Because api_key is accepted directly by the REST API as a bearer credential, this yields full administrative control of the application. This bypasses the fix for CVE-2026-89012, which added only a strtolower() call and did not address prefix depth. The same denylist also omits pass_temp, which stores a password in cleartext, as well as national_registration_number, salary, birth, address, personal_mobile and note_private. | ||||
| CVE-2026-133481 | 1 Dolibarr | 2 Dolibarr Erp/crm, Dolibarr Erp\/crm | 2026-11-20 | 4.3 Medium |
| In Dolibarr before 24.0.3, /api/index.php/eventattendees discloses attendee and project data regardless of the caller's permissions. Only 22.0.0 and later (where api_eventattendees.class.php exists) are affected. A remote authenticated user can obtain column values one character at a time. | ||||
| CVE-2026-104927 | 2 Kingaddons, Wordpress-extensions | 2 King Addons For Elementor, King Addons For Elementor | 2026-11-20 | 7.5 High |
| The King Addons for Elementor – 100+ Elementor Widgets, 4 000+ Elementor Templates, WooCommerce Builder, Mega Menu, Popup Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 51.1.89. 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 read arbitrary post meta values — including private contact data, API keys, license keys, and plugin-internal metadata — for any published post by supplying an arbitrary meta key name via the unauthenticated AJAX endpoint. The nonce check present in the handler provides no effective barrier because the nonce is emitted into every front-end page for logged-out visitors via wp_localize_script. | ||||