Export limit exceeded: 415459 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 415459 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (415459 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-99066 | 1 Linux | 2 Linux, Linux Kernel | 2026-10-27 | 5.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: can: dev: init_can_skb(): restore skb header initialization Commit 9f10374bb024 ("can: remove private CAN skb headroom infrastructure") removed the skb_reset_mac_header()/skb_reset_network_header()/ skb_reset_transport_header() calls from init_can_skb(). As a result, RX skbs from alloc_can_skb() and friends again carry mac_header = 0xFFFF. When such an skb reaches packet_rcv_spkt() (SOCK_PACKET), the push length calculation overflows and triggers skb_under_panic -> kernel BUG -> full machine panic. The same issue was originally reported in 2014 on linux-can and fixed by commit 969439016d2c ("can: add missing initialisations in CAN related skbuffs"). packet_rcv_spkt() itself has never been hardened: only packet_rcv() and tpacket_rcv() gained dev_has_header() checks in commit d549699048b4 ("net/packet: fix packet receive on L3 devices without visible hard header"). | ||||
| CVE-2026-13162 | 2026-10-27 | N/A | ||
| An OS command vulnerability exists in CoreTec product that allows authenticated users with certain roles to execute arbitrary system commands with full control over the device. The vulnerability exists in the configuration daemon's time synchronization handler, which is responsible for setting the system time-zone. When processing time-zone configuration updates, the daemon constructs a shell command by concatenating user-supplied input without any sanitization or validation. | ||||
| CVE-2026-47486 | 2026-10-27 | 7.8 High | ||
| NVIDIA PhysX for all platforms contains a vulnerability where an attacker could cause an out-of-bounds write. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, information disclosure. | ||||
| CVE-2026-100752 | 2 Ordasoft, Ordasoft.com | 2 Real Estate Manager, Real Estate Manager (free) Extension For Joomla | 2026-10-27 | 9.8 Critical |
| Joomla Extension - ordasoft.com - Unauthenticated SQL Injection in Real Estate Manager (Free) < 6.7.9 - site/realestatemanager.php builds the ORDER BY clause of three separate frontend property-listing queries (category browsing, search results, and the full property listing) from a request-controlled order_field parameter, concatenated directly into an unquoted SQL clause with no allow-list of real column names and no cast. | ||||
| CVE-2026-15723 | 1 Gitlab | 1 Gitlab | 2026-10-27 | 8.2 High |
| GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when OmniAuth SAML and LDAP auto-linking were both enabled, an authenticated user could have taken over an existing LDAP-backed account without any interaction from the targeted user, due to improper input sanitization in the LDAP email lookup path used during OmniAuth identity linking. | ||||
| CVE-2026-13319 | 1 Gitlab | 1 Gitlab | 2026-10-27 | 4.3 Medium |
| GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.10 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, could have allowed an authenticated to read milestone metadata, including titles, descriptions, and full project paths, from arbitrary private projects across the instance without any project membership, due to missing authorization checks on a user-supplied project filter parameter in the group milestones API. | ||||
| CVE-2026-12664 | 1 Gitlab | 1 Gitlab | 2026-10-27 | 6.8 Medium |
| GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, could have allowed an authenticated user with a read_api-scoped token to retrieve a project's incoming email address and create work items, bypassing the token's restrictions, due to insufficient scope enforcement on a GraphQL field. | ||||
| CVE-2026-112326 | 1 Gitlab | 1 Gitlab | 2026-10-27 | 3.1 Low |
| GitLab has remediated an issue in GitLab EE affecting all versions from 17.8 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, could have allowed an authenticated user with read-only permissions to permanently delete existing vulnerability records due to improper cleanup logic that failed to distinguish between pre-existing records from newly created ones during error handling. | ||||
| CVE-2026-112212 | 1 Gitlab | 1 Gitlab | 2026-10-27 | 7.5 High |
| GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, an unauthenticated user could have poisoned a shared cache's OAuth/OIDC discovery document to redirect certain flows to an externally controlled server, due to improper trust of user-supplied values when constructing endpoint URLs in cached discovery responses. | ||||
| CVE-2026-110264 | 1 Gitlab | 1 Gitlab | 2026-10-27 | 10 Critical |
| An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before 19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server due to integer overflow when compiling a specially crafted regular expression. | ||||
| CVE-2026-105777 | 1 Gitlab | 1 Gitlab | 2026-10-27 | 4.3 Medium |
| GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6.5 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, an unauthenticated user could have retrieved sensitive internal server credentials due to improper filtering of internal response headers. | ||||
| CVE-2026-109708 | 1 Mozilla | 1 Firefox | 2026-10-27 | 9.6 Critical |
| Sandbox escape due to incorrect boundary conditions in the Networking component. This vulnerability was fixed in Firefox 158, Firefox ESR 153.5, Thunderbird 158, Thunderbird 153.5, and Firefox ESR 115.44. | ||||
| CVE-2026-117986 | 2026-10-27 | N/A | ||
| Use-after-free in the Graphics component. This vulnerability was fixed in Firefox 159 and Firefox ESR 153.6. | ||||
| CVE-2026-105711 | 1 Gitlab | 1 Gitlab | 2026-10-27 | 3.5 Low |
| GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when a merge request in a public project referenced a confidential issue from a private project, an authenticated user with no project membership could have read the confidential issue's title, due to a viewer-independent fragment cache key that incorrectly shared per-user-redacted rendered content across all users. | ||||
| CVE-2026-117977 | 2026-10-27 | N/A | ||
| Other issue in the Console component. This vulnerability was fixed in Firefox 159 and Firefox ESR 153.6. | ||||
| CVE-2026-117976 | 2026-10-27 | N/A | ||
| Site isolation issue in the DOM: Navigation component. This vulnerability was fixed in Firefox 159 and Firefox ESR 153.6. | ||||
| CVE-2026-117970 | 2026-10-27 | N/A | ||
| Race condition in the Disability Access APIs component. This vulnerability was fixed in Firefox 159 and Firefox ESR 153.6. | ||||
| CVE-2026-117968 | 2026-10-27 | N/A | ||
| Use-after-free in the DOM: Core & HTML component. This vulnerability was fixed in Firefox 159, Firefox ESR 115.44, and Firefox ESR 153.6. | ||||
| CVE-2026-117965 | 2026-10-27 | N/A | ||
| Same-origin policy bypass in the Address Bar component. This vulnerability was fixed in Firefox 159 and Firefox ESR 153.6. | ||||
| CVE-2026-117962 | 2026-10-27 | N/A | ||
| Sandbox escape due to incorrect boundary conditions in the Storage: Quota Manager component. This vulnerability was fixed in Firefox 159 and Firefox ESR 153.6. | ||||