Export limit exceeded: 427672 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 427672 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (427672 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-64544 | 1 Linux | 1 Linux Kernel | 2026-11-17 | 7.1 High |
| In the Linux kernel, the following vulnerability has been resolved: crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents pefile_digest_pe_contents() computes the trailing-data hash length as pelen - (hashed_bytes + certs_size). A crafted PE can make the addition exceed pelen, causing the unsigned subtraction to underflow to ~4 GiB. This is passed to crypto_shash_update() which reads out of bounds and panics on unmapped vmalloc guard pages. BUG: unable to handle page fault for address: ffffc900038d8000 Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: 0010:sha256_blocks_generic (lib/crypto/sha256.c:152) Call Trace: <TASK> __sha256_update (lib/crypto/sha256.c:208) crypto_sha256_update (crypto/sha256.c:142) verify_pefile_signature (crypto/asymmetric_keys/verify_pefile.c:436) kexec_kernel_verify_pe_sig (kernel/kexec_file.c:151) __do_sys_kexec_file_load (kernel/kexec_file.c:406) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) </TASK> Kernel panic - not syncing: Fatal exception Validate that the addition does not overflow and the result does not exceed pelen before the subtraction. Return -ELIBBAD on failure. | ||||
| CVE-2026-64553 | 1 Linux | 1 Linux Kernel | 2026-11-17 | 5.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: net: psample: fix info leak in PSAMPLE_ATTR_DATA psample open codes nla_put() presumably to avoid wiping the data with 0s just to override it with packet data. This open coding is missing clearing the pad, however, each netlink attr is padded to 4B and data_len may not be divisible by 4B. | ||||
| CVE-2026-21170 | 2026-11-17 | N/A | ||
| Improper enforcement of behavioral workflow in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to write arbitrary files with Smart Switch privilege. | ||||
| CVE-2026-21172 | 2026-11-17 | N/A | ||
| Incomplete cleanup in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to establish an unauthorized connection. | ||||
| CVE-2026-126828 | 2026-11-17 | 6.7 Medium | ||
| A vulnerability in Phison SSD controller firmwares (Phison E18; EIFM80.0, Phison E18; EIFK51.2) allows a local attacker with administrative privileges to bypass the "Security Access" handshake by leveraging leaked RSA parameters found in vendor utility binaries. By successfully completing the authentication, an attacker can access vendor-specific commands that permit arbitrary memory read and write operations. Because the firmware's code regions lack protection, these primitives can be used to overwrite existing handlers and achieve volatile code execution on the SSD controller. | ||||
| CVE-2026-129190 | 2026-11-17 | 6.7 Medium | ||
| A vulnerability in the Phison SSD controller firmware Phison E12; ECFM32.2 allows a local attacker with administrative privileges to bypass the "Security Access" handshake by leveraging leaked RSA parameters found in vendor utility binaries. By successfully completing the authentication, an attacker can access vendor-specific commands that permit arbitrary memory read and write operations. Because the firmware's code regions lack protection, these primitives can be used to overwrite existing handlers and achieve volatile code execution on the SSD controller. | ||||
| CVE-2026-129187 | 2026-11-17 | 6.7 Medium | ||
| A vulnerability in the Phison SSD controller firmware Phison E16; EGFM13.2 allows a local attacker with administrative privileges to bypass the "Security Access" handshake by leveraging leaked RSA parameters found in vendor utility binaries. By successfully completing the authentication, an attacker can access vendor-specific commands that permit arbitrary memory read and write operations. Because the firmware's code regions lack protection, these primitives can be used to overwrite existing handlers and achieve volatile code execution on the SSD controller. | ||||
| CVE-2026-127138 | 2026-11-17 | N/A | ||
| pretix provides a mechanism where ticket QR codes are cryptographically signed and can be verified by our pretixSCAN apps in offline mode without any database of valid tickets. pretixSCAN checks the signature to verify that the ticket was issued by the correct pretix event and compares the QR code against a list of revoked QR codes. A QR code becomes revoked when the order is canceled, or the ticket is changed in a way that a new QR code needs to be generated. However, the parsing of the QR code in all of our pretixSCAN apps contained a faulty computation, rendering the check for the correct length of the contents faulty. This way, an attacker is able to craft multiple QR codes for the same ticket which have the same content, but look different and therefore do not match against the revocation list. This does not allow to fabricate entirely new tickets, but it does allow to enter the event with e.g. a canceled ticket. This attack requires pretixSCAN to be scanning in offline mode and the "pretix signature scheme 1" to be used for the event's QR codes. If the attack is executed, the ticket unfortunately shows as valid (green) on the scanner but as invalid (red) on the server since the server later cannot match it to a ticket. We scanned the entire database of scans on pretix Hosted and could not find any traces of this being exploited in the past. | ||||
| CVE-2026-129246 | 2026-11-17 | 7.8 High | ||
| Due to a Debian-specific patch, the directory used to share data between the LightDM and the users logging in was writable by the lightdm user of the unprivileged greeter process. A process running under the lightdm identity could leverage write access to that directory to force the LightDM process (running as root) to change ownership and permissions on other root-owned directories and escalate privileges from the lightdm user to root. | ||||
| CVE-2026-21602 | 2026-11-17 | N/A | ||
| This High severity Stored XSS vulnerability was introduced in version 10.3.26 of Jira Core Data Center and Jira Software Data Center. This Stored XSS vulnerability, with a CVSS Score of 7.4, allows an authenticated attacker to execute arbitrary HTML or JavaScript code on a victims browser. Atlassian recommends that Jira Core Data Center and Jira Software Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Jira Core Data Center and Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 * Jira Core Data Center and Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://www.atlassian.com/software/jira/download-archives). You can download the latest version of Jira Core Data Center and Jira Software Data Center from the download center (https://www.atlassian.com/software/jira/download-archives). This vulnerability was reported via our Penetration Testing program. | ||||
| CVE-2026-77941 | 1 Autodesk | 1 Autocad | 2026-11-17 | 3.3 Low |
| A maliciously crafted DWG or DXF file containing an external reference with an attacker-controlled network path, when parsed through Autodesk AutoCAD, can force an Information Disclosure vulnerability. A malicious actor can leverage this vulnerability to disclose NTLM authentication information from the current user. | ||||
| CVE-2026-77944 | 1 Autodesk | 1 Autocad | 2026-11-17 | 3.3 Low |
| A maliciously crafted DXF file containing a scene-background object with an attacker-controlled network path, when parsed through Autodesk AutoCAD, can force an Information Disclosure vulnerability. A malicious actor can leverage this vulnerability to disclose NTLM authentication information from the current user. | ||||
| CVE-2026-28273 | 1 Zoneminder | 1 Zoneminder | 2026-11-17 | 9.9 Critical |
| ZoneMinder is a free, open source closed-circuit television software application. Prior to 1.38.4, any authenticated user can use the /api/configs/edit/{name}.json endpoint to modify protected configuration settings because ConfigsController::edit() does not enforce the System=Edit authorization requirement and its system-variable protection is ineffective. An attacker can set ZM_PATH_FFMPEG to a command-bearing value and trigger an exec() sink in web/views/image.php or web/includes/Event.php by requesting frame extraction. This permits arbitrary command execution with the privileges of the web server user and can expose private camera feeds, recordings, and database data or establish persistence. This issue is fixed in version 1.38.4. | ||||
| CVE-2026-77940 | 1 Autodesk | 1 Autocad | 2026-11-17 | 3.3 Low |
| A maliciously crafted DWG file containing an attacker-controlled network path, when parsed through Autodesk AutoCAD, can force an Information Disclosure vulnerability. A malicious actor can leverage this vulnerability to disclose NTLM authentication information from the current user. | ||||
| CVE-2026-93298 | 1 Autodesk | 1 Autocad | 2026-11-17 | 5.5 Medium |
| A maliciously crafted DXF file containing crafted VBA project data, when parsed through Autodesk AutoCAD, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to read sensitive data from process memory. | ||||
| CVE-2026-95849 | 1 Linkwarden | 1 Linkwarden | 2026-11-17 | 6.8 Medium |
| Linkwarden is a self-hosted, open-source collaborative bookmark manager to collect, organize and archive webpages. Prior to 2.15.0, .github/workflows/check-branch.yml runs on the privileged pull_request_target event and interpolates the attacker-controlled github.head_ref source branch name unquoted into a run: shell script. An unauthenticated attacker can open a pull request from a fork with shell metacharacters in its branch name, causing arbitrary commands to execute in the base repository's privileged CI job before the branch comparison result matters. The job has access to GITHUB_TOKEN and any exposed secrets, allowing secret exfiltration and, when workflow token permissions allow repository writes, modification of repository content. This issue is fixed in version 2.15.0. | ||||
| CVE-2026-82150 | 1 Dell | 1 Supportassist Os Recovery | 2026-11-17 | 8 High |
| Dell SupportAssist OS Recovery, versions prior to 5.5.16.3, contain an Insufficient Verification of Data Authenticity vulnerability. An unauthenticated attacker with adjacent network access could potentially exploit this vulnerability to bypass manifest signature validation, potentially leading to execution of unauthorized code with elevated privileges. | ||||
| CVE-2026-82138 | 1 Dell | 1 Supportassist Os Recovery | 2026-11-17 | 7.4 High |
| Dell SupportAssist OS Recovery, versions prior to 5.5.16.3 contain a Download of Code Without Integrity Check vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Code execution. | ||||
| CVE-2026-82139 | 1 Dell | 1 Supportassist Os Recovery | 2026-11-17 | 7.4 High |
| Dell SupportAssist OS Recovery, versions prior to 5.5.16.3, contain an Improper Certificate Validation vulnerability. An unauthenticated attacker with local access could potentially exploit this vulnerability, leading to Protection mechanism bypass. | ||||
| CVE-2026-95822 | 1 Zephyrproject | 1 Zephyr | 2026-11-17 | 3.3 Low |
| The SOCKS5 client in subsys/net/lib/socks/socks.c built the CONNECT request in socks5_tcp_connect() by choosing the SOCKS5 address type from the address family of the proxy (proxy->sa_family) while reading the bytes out of the destination address supplied to connect(). A SOCKS5 request encodes the destination independently of the transport used to reach the proxy, so the two families are unrelated and nothing in the path forces them to agree: set_context_proxy() only requires the proxy family to match the socket, and zsock_connect_ctx() enters the SOCKS branch before any destination validation. With an IPv6 proxy and an AF_INET destination the code treated an 8-byte struct net_sockaddr_in as a struct net_sockaddr_in6 and copied the 16-byte sin6_addr from it, reading 12 bytes past the end of the object and transmitting them to the proxy. With CONFIG_USERSPACE enabled, z_vrfy_zsock_connect() copies only addrlen user bytes into a stack-resident struct net_sockaddr_storage and enforces no per-family minimum length, so the oversized read stays within the storage but returns stale, uninitialised kernel-stack bytes. An unprivileged user-mode thread can therefore open an AF_INET6 stream socket, point setsockopt(SO_SOCKS5) at a proxy it controls, and call connect() with a short AF_INET destination to have the kernel send it 12 bytes of supervisor stack residue per attempt. Without CONFIG_USERSPACE the read runs past the end of the caller's own struct net_sockaddr_in, disclosing adjacent memory to the proxy; the family mismatch can arise unintentionally when a destination is obtained from DNS while an IPv6 proxy is configured. Impact is limited to information disclosure of at most 12 bytes per connect() call, with no write primitive; the leak is delivered to whoever operates the SOCKS5 proxy. The mirrored pairing (IPv6 destination through an IPv4 proxy) is memory-safe but encoded the destination as SOCKS5_ATYP_IPV4 from the first four bytes of the IPv6 address, causing the proxy to connect to an unrelated host. Exploitation requires the non-default CONFIG_SOCKS option, a socket with SO_SOCKS5 configured, and both IPv4 and IPv6 support in the image. The fix moves the encoding into a helper that selects the address type from dest->sa_family and validates dest_len against the matching struct net_sockaddr_in/struct net_sockaddr_in6 before copying, rejecting under-length or unsupported destinations with an error. | ||||