Export limit exceeded: 430483 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430483 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-130449 | 2 Wireshark, Wireshark Foundation | 2 Wireshark, Wireshark | 2026-11-21 | 5.5 Medium |
| TLS protocol dissector memory leak in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-130452 | 2 Wireshark, Wireshark Foundation | 2 Wireshark, Wireshark | 2026-11-21 | 5.5 Medium |
| USB-PTP protocol dissector crash in 4.6.0 to 4.6.9 allows denial of service | ||||
| CVE-2026-130602 | 2026-11-21 | 7.1 High | ||
| Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in BdThemes Prime Slider – Addons For Elementor bdthemes-prime-slider-lite allows Stored XSS.This issue affects Prime Slider – Addons For Elementor: from n/a through 5.1.2. | ||||
| CVE-2026-76466 | 1 Cisco | 2 Expressway, Expressway Series | 2026-11-21 | 9.8 Critical |
| A vulnerability in the database service feature of Cisco Expressway Series could allow an unauthenticated, remote attacker with network access to a Cisco Expressway device to execute arbitrary operating system commands as root. This vulnerability is due to the use of persistent cookies. Additionally, there is insufficient validation of client certificates when the TLS Verify Mode is set to Enabled for clustering, which means that client certificates are not validated. An attacker with possession of the cookies could exploit this vulnerability by connecting to the database service and invoking specific remote procedure call (RPC) commands. A successful exploit could allow the attacker to execute arbitrary commands as root on the underlying operating system of an affected device. Note: Cisco Expressway Series refers to Cisco Expressway Core (Expressway-C) devices and Cisco Expressway Edge (Expressway-E) devices. | ||||
| CVE-2026-48728 | 1 Glpi-project | 1 Glpi-inventory-plugin | 2026-11-21 | N/A |
| The GLPI Inventory Plugin handles network discovery, inventory, software deployment, and data collection for GLPI agents. Prior to 1.6.8, the /b/deploy, /b/collect, and /b/esx agent API endpoints do not authenticate requests before processing Deploy, Collect, and ESX task operations. An unauthenticated remote attacker can enumerate jobs and manipulate their status through these endpoints, disclosing job information and interfering with task processing. This issue is fixed in version 1.6.8. | ||||
| CVE-2026-133958 | 1 Redhat | 1 Quay | 2026-11-21 | 5.5 Medium |
| A flaw was found in Quay. Insufficient validation of repository notification webhook URLs allows an authenticated administrator to trigger Server-Side Request Forgery (SSRF). By specifying an internal URL or a redirect to an internal destination, an attacker can force the Quay worker to issue unauthorized HTTP requests to internal network locations and cloud metadata services. | ||||
| CVE-2026-132224 | 1 Optimizely | 1 Web Experimentation | 2026-11-21 | N/A |
| Optimizely Web Experimentation before 2026-11-17 mishandles the account signup flow, leading to presence of attacker-controlled code in the projectJS (aka Project JavaScript) field of certain cdn.optimizely.com assets. | ||||
| CVE-2026-131239 | 1 Splunk | 1 Enterprise Security | 2026-11-21 | 7.3 High |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in Updates data. If another user who can access the System Update Status report selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify data available to the user who selects the row. The vulnerability is possible because the System Update Status report does not validate destination, signature, and vendor-product values before inserting them into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and System Update Status (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/system-update-status) in the Splunk documentation. | ||||
| CVE-2026-131209 | 1 Splunk | 1 Enterprise Security | 2026-11-21 | 8.3 High |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_ers_execution_post capability could cause the User and Entity Behavior Analytics (UEBA) Content App to run arbitrary Search Processing Language (SPL) commands with elevated permissions through an Entity Risk Score calculation. With this access, the user could expose stored credentials and other data outside the permissions assigned to that role. The vulnerability is possible because the UEBA Content App does not validate Entity Risk Score calculation values before including them in SPL searches. For more information see Installing the UEBA Content App for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.5/user-and-entity-behavior-analytics/installing-the-ueba-content-app-for-splunk-enterprise-security), Entity risk scoring in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/risk-based-alerting/entity-risk-scoring-in-splunk-enterprise-security), and Roles and knowledge objects in UEBA for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.8/user-and-entity-behavior-analytics/ueba-content-app-for-on-premises/roles-and-knowledge-objects-in-ueba-for-splunk-enterprise-security) in the Splunk documentation. | ||||
| CVE-2026-131202 | 1 Splunk | 1 Enterprise Security | 2026-11-21 | 9.1 Critical |
| In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_admin" Splunk Enterprise Security role could execute arbitrary code on the search head as the user account running Splunk Enterprise by combining lookup file upload and Configuration Checker functionality. The vulnerability is possible because Splunk Enterprise Security does not restrict lookup upload file types or keep Configuration Checker module paths within the intended directory. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Create and manage lookups in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/managing-security-content/create-and-manage-lookups-in-splunk-enterprise-security) in the Splunk documentation. | ||||
| CVE-2026-131199 | 1 Splunk | 1 Enterprise Security | 2026-11-21 | 8.8 High |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could cause the Risk Event Timeline Representational State Transfer (REST) API to run arbitrary Search Processing Language (SPL) commands with elevated permissions. With this access, the user could expose stored credentials and modify indexes and lookup data available to those permissions. The vulnerability is possible because the affected REST API does not validate request values before including them in search macro arguments. For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Risk analysis (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/risk-analysis) in the Splunk documentation. | ||||
| CVE-2026-129448 | 1 Apache | 1 Roller | 2026-11-21 | 9.8 Critical |
| Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. Users who cannot upgrade right away should set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, and restart Roller. Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting. | ||||
| CVE-2026-123890 | 1 Vmware | 5 Cloud Foundation, Telco Cloud Infrastructure, Telco Cloud Platform and 2 more | 2026-11-21 | 9.8 Critical |
| VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service. Affected versions: 9.1.x (fixed in 9.1.1.0200); 9.0.x (fixed in 9.0.2.0200); 8.0 (fixed in 8.0 U3m); 5.x (fixed in 5.2.5). Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 and Telco Cloud Infrastructure 3.0 are also affected (see KB463116). | ||||
| CVE-2025-42884 | 1 Sap | 1 Netweaver Enterprise Portal | 2026-11-21 | 6.5 Medium |
| SAP NetWeaver Enterprise Portal allows an unauthenticated attacker to inject JNDI environment properties or pass a URL used during JNDI lookup operations, enabling access to an unintended JNDI provider.�This could further lead to disclosure or modification of information about the server. There is no impact on availability. | ||||
| CVE-2026-129409 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Open redirects in data view controller and after form submission in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - Return and redirect URLs taken from user input in the data/PDF controller and after a successful form submission were not validated, allowing redirects to external sites. | ||||
| CVE-2026-129413 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - IDOR in backend data export in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - The backend export did not correctly verify permissions for the exported form, allowing backend users to export data of forms they are not authorized to access. | ||||
| CVE-2026-129402 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Unauthenticated SQL injection in reload task in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - Input placeholders in SQL field statements were inserted without quoting in the public reload task, allowing unauthenticated SQL injection in read queries. | ||||
| CVE-2026-129401 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Open redirect on invalid form submission in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The return parameter of an invalid form submission was not validated, allowing redirects to external sites. | ||||
| CVE-2026-129397 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Arbitrary file deletion via path traversal in CSS editor in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The delete and rename tasks of the CSS editor lacked authorization checks, CSRF protection and path validation, allowing backend users to delete files outside the CSS directory. | ||||
| CVE-2026-129396 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Arbitrary file write leading to remote code execution in CSS editor in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The CSS editor did not restrict file names, extensions and paths of created and saved files, allowing privileged backend users to write arbitrary PHP files. | ||||