2026-05-01
2026-05-01 16:16Z
CRIT

CVE-2026-42472 — Unsafe: deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17.

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-42472

Unsafe deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17. The session and cache handlers use unserialize() on data from Redis in the RedisHandler object. CVSSv3.1 9.8 (CRITICAL)

CWECWE 502VNDUnsafeTYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-05-01
2026-05-01 16:16Z
HIGH

CVE-2026-42471 — Unsafe: deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17.

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-42471

Unsafe deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17. The sync-invoke client (Connection.php:76) calls unserialize() on data received from the server response, enabling client-side RCE if connecting to a malicious server. CVSSv3.1 8.1 (HIGH)

CWECWE 502VNDUnsafeTYPVulnerability
8.1
CVSS v3.1
91
Edit Score
2026-05-01
2026-05-01 16:16Z
HIGH

CVE-2026-37552 — Unsafe: deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17.

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-37552

Unsafe deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17. The sync-invoke TCP server (Server.php:87) receives data from a TCP socket, passes it directly to Opis\Closure\unserialize(), then executes the result via call_user_func(). No authentication or signature verification exists on the TCP connection. An attacker with access to the localhost TCP port (server binds 127.0.0.1) can send a crafted serialized PHP closure to achieve arbitrary code execution. CVSSv3.1 8.4 (HIGH)

VNDUnsafeTYPVulnerability
8.4
CVSS v3.1
92
Edit Score
2026-05-01
2026-05-01 16:16Z
CRIT

CVE-2026-22166 — On certain platforms, when the process executing graphics workload has system privileges this could

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-22166

A web page that contains unusual WebGPU content loaded into the GPU GLES render process and can trigger write UAF crash in the GPU GLES user-space shared library. On certain platforms, when the process executing graphics workload has system privileges this could enable subsequent exploit on the system. CVSSv3.1 9.6 (CRITICAL)

CWECWE 416TYPVulnerability
9.6
CVSS v3.1
98
Edit Score
2026-05-01
2026-05-01 16:16Z
HIGH

CVE-2026-22165 — On certain platforms, when the process executing graphics workload has system privileges this could

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-22165

A web page that contains unusual WebGPU content loaded into the GPU GLES render process and can trigger a write UAF crash in the GPU GLES user-space shared library. On certain platforms, when the process executing graphics workload has system privileges this could enable further exploits on the device. CVSSv3.1 8.1 (HIGH)

CWECWE 416TYPVulnerability
8.1
CVSS v3.1
91
Edit Score
2026-05-01
2026-05-01 15:16Z
HIGH

CVE-2026-43051 — Linux: In the Linux kernel, the following vulnerability has been resolved: HID: wacom: fix out-of-bounds

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-43051

In the Linux kernel, the following vulnerability has been resolved: HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq The wacom_intuos_bt_irq() function processes Bluetooth HID reports without sufficient bounds checking. A maliciously crafted short report can trigger an out-of-bounds read when copying data into the wacom structure. Specifically, report 0x03 requires at least 22 bytes to safely read the processed data and battery status, while report 0x04 (which fal CVSSv3.1 8.1 (HIGH) · EPSS 7th percentile

TYPVulnerability
8.1
CVSS v3.1
91
Edit Score
2026-05-01
2026-05-01 15:16Z
HIGH

CVE-2026-43048 — Linux: However, as we have previously seen, doing so can easily result in OOB reads

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-43048

In the Linux kernel, the following vulnerability has been resolved: HID: core: Mitigate potential OOB by removing bogus memset() The memset() in hid_report_raw_event() has the good intention of clearing out bogus data by zeroing the area from the end of the incoming data string to the assumed end of the buffer. However, as we have previously seen, doing so can easily result in OOB reads and writes in the subsequent thread of execution. The current suggestion from one of t CVSSv3.1 8.8 (HIGH) · EPSS 4th percentile

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
728 × 90 / responsive · programmatic ad slot
2026-05-01
2026-05-01 15:16Z
CRIT

CVE-2026-43039 — Linux: In the Linux kernel, the following vulnerability has been resolved: net: ti: icssg-prueth: fix

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-43039

In the Linux kernel, the following vulnerability has been resolved: net: ti: icssg-prueth: fix missing data copy and wrong recycle in ZC RX dispatch emac_dispatch_skb_zc() allocates a new skb via napi_alloc_skb() but never copies the packet data from the XDP buffer into it. The skb is passed up the stack containing uninitialized heap memory instead of the actual received packet, leaking kernel heap contents to userspace. Copy the received packet data from the XDP buffer in CVSSv3.1 9.8 (CRITICAL)

TYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-05-01
2026-05-01 15:16Z
CRIT

CVE-2026-43038 — Linux: In the Linux kernel, the following vulnerability has been resolved: ipv6: icmp: clear skb2->cb[]

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-43038

In the Linux kernel, the following vulnerability has been resolved: ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() Sashiko AI-review observed: In ip6_err_gen_icmpv6_unreach(), the skb is an outer IPv4 ICMP error packet where its cb contains an IPv4 inet_skb_parm. When skb is cloned into skb2 and passed to icmp6_send(), it uses IP6CB(skb2). IP6CB interprets the IPv4 inet_skb_parm as an inet6_skb_parm. The cipso offset in inet_skb_parm.opt directly o CVSSv3.1 9.8 (CRITICAL) · EPSS 7th percentile

TYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-05-01
2026-05-01 15:16Z
CRIT

CVE-2026-43037 — Linux: In the Linux kernel, the following vulnerability has been resolved: ip6_tunnel: clear skb2->cb[] in

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-43037

In the Linux kernel, the following vulnerability has been resolved: ip6_tunnel: clear skb2->cb[] in ip4ip6_err() Oskar Kjos reported the following problem. ip4ip6_err() calls icmp_send() on a cloned skb whose cb[] was written by the IPv6 receive path as struct inet6_skb_parm. icmp_send() passes IPCB(skb2) to __ip_options_echo(), which interprets that cb[] region as struct inet_skb_parm (IPv4). The layouts differ: inet6_skb_parm.nhoff at offset 14 overlaps inet_skb_parm.opt CVSSv3.1 9.8 (CRITICAL) · EPSS 7th percentile

TYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-05-01
2026-05-01 15:16Z
HIGH

CVE-2026-43018 — Linux: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: fix potential

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-43018

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt hci_conn lookup and field access must be covered by hdev lock in hci_le_remote_conn_param_req_evt, otherwise it's possible it is freed concurrently. Extend the hci_dev_lock critical section to cover all conn usage. CVSSv3.1 8.8 (HIGH) · EPSS 7th percentile

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-05-01
2026-05-01 15:16Z
CRIT

CVE-2026-43011 — Linux: In the Linux kernel, the following vulnerability has been resolved: net/x25: Fix potential double

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-43011

In the Linux kernel, the following vulnerability has been resolved: net/x25: Fix potential double free of skb When alloc_skb fails in x25_queue_rx_frame it calls kfree_skb(skb) at line 48 and returns 1 (error). This error propagates back through the call chain: x25_queue_rx_frame returns 1 | v x25_state3_machine receives the return value 1 and takes the else branch at line 278, setting queued=0 and returning 0 | v x25_process_rx_frame returns queued=0 | CVSSv3.1 9.8 (CRITICAL) · EPSS 7th percentile

TYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-05-01
2026-05-01 15:16Z
HIGH

CVE-2026-31779 — Linux: In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31779

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() The memcpy function assumes the dynamic array notif->matches is at least as large as the number of bytes to copy. Otherwise, results->matches may contain unwanted data. To guarantee safety, extend the validation in one of the checks to ensure sufficient packet length. Found by Linux Verification Center (linuxtesting.org CVSSv3.1 8.1 (HIGH)

TYPVulnerability
8.1
CVSS v3.1
91
Edit Score
2026-05-01
2026-05-01 15:16Z
HIGH

CVE-2026-31773 — Linux: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SMP: derive legacy

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31773

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SMP: derive legacy responder STK authentication from MITM state The legacy responder path in smp_random() currently labels the stored STK as authenticated whenever pending_sec_level is BT_SECURITY_HIGH. That reflects what the local service requested, not what the pairing flow actually achieved. For Just Works/Confirm legacy pairing, SMP_FLAG_MITM_AUTH stays clear and the resulting STK should rem CVSSv3.1 8.8 (HIGH) · EPSS 14th percentile

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-05-01
2026-05-01 15:16Z
HIGH

CVE-2026-31771 — Linux: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: move wake

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31771

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: move wake reason storage into validated event handlers hci_store_wake_reason() is called from hci_event_packet() immediately after stripping the HCI event header but before hci_event_func() enforces the per-event minimum payload length from hci_ev_table. This means a short HCI event frame can reach bacpy() before any bounds check runs. Rather than duplicating skb parsing and per-event CVSSv3.1 8.1 (HIGH) · EPSS 6th percentile

TYPVulnerability
8.1
CVSS v3.1
91
Edit Score
2026-05-01
2026-05-01 15:16Z
HIGH

CVE-2026-31739 — Linux: In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - Add

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31739

In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - Add missing CRYPTO_ALG_ASYNC The tegra crypto driver failed to set the CRYPTO_ALG_ASYNC on its asynchronous algorithms, causing the crypto API to select them for users that request only synchronous algorithms. This causes crashes (at least). Fix this by adding the flag like what the other drivers do. Also remove the unnecessary CRYPTO_ALG_TYPE_* flags, since those just get ignored and over CVSSv3.1 8.8 (HIGH) · EPSS 5th percentile

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-05-01
2026-05-01 15:16Z
HIGH

CVE-2026-31735 — Linux: In the Linux kernel, the following vulnerability has been resolved: iommupt: Fix short gather

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31735

In the Linux kernel, the following vulnerability has been resolved: iommupt: Fix short gather if the unmap goes into a large mapping unmap has the odd behavior that it can unmap more than requested if the ending point lands within the middle of a large or contiguous IOPTE. In this case the gather should flush everything unmapped which can be larger than what was requested to be unmapped. The gather was only flushing the range requested to be unmapped, not extending to the CVSSv3.1 8.8 (HIGH) · EPSS 5th percentile

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-05-01
2026-05-01 14:16Z
CRIT

CVE-2026-42484 — Hashcat Hashcat: A heap-based buffer overflow in hex_to_binary in the PKZIP hash parser in hashcat v7.1.2

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-42484

A heap-based buffer overflow in hex_to_binary in the PKZIP hash parser in hashcat v7.1.2 allows an attacker to cause a denial of service or possibly execute arbitrary code via a crafted PKZIP hash file. The issue affects modules 17200, 17210, 17220, 17225, and 17230. When data_type_enum<=1, attacker-controlled hex data from a user-supplied hash string is decoded into a fixed-size buffer without proper input-length validation. CVSSv3.1 9.8 (CRITICAL)

CWECWE 787VNDHashcatTYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-05-01
2026-05-01 14:16Z
CRIT

CVE-2026-42483 — Hashcat Hashcat: A heap-based buffer overflow in the Kerberos hash parser in hashcat v7.1.2 allows an

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-42483

A heap-based buffer overflow in the Kerberos hash parser in hashcat v7.1.2 allows an attacker to cause a denial of service or possibly execute arbitrary code via a crafted Kerberos hash file. The issue affects module_hash_decode in multiple Kerberos-related modules because account_info_len is calculated from untrusted delimiter positions without upper-bound validation before memcpy copies the data into a fixed-size account_info buffer. CVSSv3.1 9.8 (CRITICAL)

CWECWE 787VNDHashcatTYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-05-01
2026-05-01 14:16Z
CRIT

CVE-2026-42482 — Hashcat Hashcat: A stack-based buffer overflow in mangle_to_hex_lower() and mangle_to_hex_upper() in src/rp_cpu.c in hashcat v7.1.2 allows

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-42482

A stack-based buffer overflow in mangle_to_hex_lower() and mangle_to_hex_upper() in src/rp_cpu.c in hashcat v7.1.2 allows an attacker to cause a denial of service or possibly execute arbitrary code via a crafted rule file, or via the -j or -k rule options used with password candidates of 128 or more characters. The vulnerability is caused by a bounds check that fails to account for the 2x expansion that occurs when password bytes are converted to hexadecimal. CVSSv3.1 9.8 (CRITICAL)

CWECWE 787VNDHashcatTYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-05-01
2026-05-01 14:16Z
CRIT

CVE-2026-31718 — Linux: In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31718

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in __ksmbd_close_fd() via durable scavenger When a durable file handle survives session disconnect (TCP close without SMB2_LOGOFF), session_fd_check() sets fp->conn = NULL to preserve the handle for later reconnection. However, it did not clean up the byte-range locks on fp->lock_list. Later, when the durable scavenger thread times out and calls __ksmbd_close_fd(NULL, fp), the loc CVSSv3.1 9.8 (CRITICAL) · EPSS 5th percentile

TYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-05-01
2026-05-01 14:16Z
HIGH

CVE-2026-31717 — Linux: This allows any authenticated user to hijack an orphaned durable handle by predicting or

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31717

In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate owner of durable handle on reconnect Currently, ksmbd does not verify if the user attempting to reconnect to a durable handle is the same user who originally opened the file. This allows any authenticated user to hijack an orphaned durable handle by predicting or brute-forcing the persistent ID. According to MS-SMB2, the server MUST verify that the SecurityContext of the reconnect request m CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-05-01
2026-05-01 14:16Z
HIGH

CVE-2026-31712 — Linux: In the Linux kernel, the following vulnerability has been resolved: ksmbd: require minimum ACE

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31712

In the Linux kernel, the following vulnerability has been resolved: ksmbd: require minimum ACE size in smb_check_perm_dacl() Both ACE-walk loops in smb_check_perm_dacl() only guard against an under-sized remaining buffer, not against an ACE whose declared `ace->size` is smaller than the struct it claims to describe: if (offsetof(struct smb_ace, access_req) > aces_size) break; ace_size = le16_to_cpu(ace->size); if (ace_size > aces_size) break; The first c CVSSv3.1 8.3 (HIGH)

TYPVulnerability
8.3
CVSS v3.1
92
Edit Score
2026-05-01
2026-05-01 14:16Z
HIGH

CVE-2026-31709 — Linux: In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31709

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the whole DACL before rewriting it in cifsacl build_sec_desc() and id_mode_to_cifs_acl() derive a DACL pointer from a server-supplied dacloffset and then use the incoming ACL to rebuild the chmod/chown security descriptor. The original fix only checked that the struct smb_acl header fits before reading dacl_ptr->size or dacl_ptr->num_aces. That avoids the immediate header-field OOB r CVSSv3.1 8.8 (HIGH) · EPSS 5th percentile

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-05-01
2026-05-01 14:16Z
HIGH

CVE-2026-31708 — Linux: In the Linux kernel, the following vulnerability has been resolved: smb: client: fix OOB

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-31708

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path smb2_ioctl_query_info() has two response-copy branches: PASSTHRU_FSCTL and the default QUERY_INFO path. The QUERY_INFO branch clamps qi.input_buffer_length to the server-reported OutputBufferLength and then copies qi.input_buffer_length bytes from qi_rsp->Buffer to userspace, but it never verifies that the flexible-array payload actually fi CVSSv3.1 8.1 (HIGH) · EPSS 5th percentile

TYPVulnerability
8.1
CVSS v3.1
91
Edit Score