Vulnerabilidades explotables hoy
367,284en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,685
Nuevos KEV · 24H0
Exploit Today ≥ 701,629
Distribución · última ventana
- Crítico2,295
- Alto9,356
- Medio5,355
- Bajo528
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-46220—2.0%
——1——CVE-2026-18679—2.0%
——1When kuma-dp is started against an HTTPS control plane and the operator did not pass a CA certificate, the data plane connects with TLS peer verification disabled, and the dataplane authentication token is sent over that unverified connection.
An on-path actor can intercept the dataplane authentication token and impersonate the control plane to the data plane, injecting a forged bootstrap configuration and taking over the proxy.13hCVE-2026-123648.4 ALT2.0%
——1The user-space system-call verifier z_vrfy_z_log_msg_static_create() in subsys/logging/log_msg.c was a pure pass-through: it forwarded the caller-supplied source, desc, package, and data arguments directly to the kernel-mode implementation z_impl_z_log_msg_static_create() without performing any of the mandatory K_SYSCALL_* checks. Because z_log_msg_static_create() is declared __syscall, under CONFIG_USERSPACE any unprivileged user-mode thread can invoke it directly with fully attacker-controlled arguments.
The kernel-mode handler dereferences each of these untrusted values: frontend_runtime_filtering() reads through the source pointer as a struct log_source_dynamic_data, cbprintf_package_copy() reads desc.package_len bytes from the package pointer, and z_log_msg_finalize() performs a memcpy() of desc.data_len bytes from the data pointer. With no verification, a user thread can supply arbitrary kernel addresses and arbitrary lengths, and the kernel will read from them.
The impact is a kernel-mode denial of service (the kernel faults dereferencing an attacker-chosen pointer) and, where a log backend output is observable to the attacker, disclosure of arbitrary kernel memory copied into the emitted log message — a confidentiality breach across the user/kernel boundary that the userspace sandbox is meant to enforce. The reads do not corrupt kernel memory, so there is no out-of-bounds write primitive.
The fix adds the required validation to the verifier: it bounds desc.package_len against Z_LOG_MSG_MAX_PACKAGE, rejects non-NULL/length mismatches, and applies K_SYSCALL_MEMORY_READ() to package, data, and (when runtime filtering with a frontend is enabled) source, so any out-of-bounds or kernel pointer now raises K_OOPS instead of being honored.6dCVE-2026-21489—1.9%
——1——CVE-2024-41750—2.0%
——1——CVE-2022-3702—2.0%
——1——CVE-2022-33217—2.0%
——1——CVE-2026-42146—2.0%
——1——CVE-2023-41833—2.0%
——1——CVE-2026-20994—2.0%
——1——CVE-2025-10491—2.0%
——1——CVE-2023-32448—2.0%
——1——CVE-2025-11964—2.0%
——1——CVE-2026-7280—2.0%
——1——CVE-2026-46235—2.0%
——1——CVE-2025-20997—2.0%
——1——CVE-2021-0439—2.0%
——1——CVE-2026-23121—2.0%
——1——CVE-2025-52516—2.0%
——1——CVE-2017-15843—2.0%
——1——CVE-2025-57836—2.0%
——1——CVE-2026-58089—2.0%
——1——CVE-2019-9375—2.0%
——1——CVE-2021-0442—2.0%
——1——CVE-2026-75904—2.0%
——1——CVE-2025-64701—2.0%
——1——CVE-2025-38388—2.0%
——1——CVE-2026-43266—2.0%
——1——CVE-2019-25310—2.0%
——1——CVE-2022-20455—2.0%
——1——CVE-2018-5849—1.9%
——1——CVE-2025-38353—2.0%
——1——CVE-2025-64343—2.0%
——1——CVE-2026-45907—2.0%
——1——CVE-2025-65083—2.0%
——1——CVE-2026-150595.5 MED2.0%
——1Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.22dCVE-2026-641835.5 MED2.0%
——1In the Linux kernel, the following vulnerability has been resolved:
efi: Allocate runtime workqueue before ACPI init
Since commit
5894cf571e14 ("acpi/prmt: Use EFI runtime sandbox to invoke PRM handlers")
ACPI PRM calls are delegated to a workqueue which runs in a kernel
thread, making it easier to detect and mitigate faulting memory accesses
performed by the firmware.
Rafael reports that such PRM accesses may occur before efisubsys_init()
executes, which is where the workqueue is allocated, leading to NULL
pointer dereferences. Since acpi_init() [which triggers the early PRM
accesses] executes as a subsys_initcall() as well, and has its own
dependencies that may be sensitive to initcall ordering, deferring
acpi_init() is not an option.
So instead, split off the workqueue allocation into its own postcore
initcall, as this is the only missing piece to allow EFI runtime calls
to be made. This ensures that EFI runtime call (including PRM calls) are
accessible to all code running at subsys_initcall() level.20dCVE-2026-40144—2.0%
——1A memory-corruption vulnerability exists in a kernel-mode component of BeyondTrust Endpoint Privilege Management (Windows deployments) prior to version 26.1.2. Insufficient validation of input processed by the component may result in memory being accessed outside its intended bounds.15dCVE-2024-0035—2.0%
——1——CVE-2026-31726—2.0%
——1——