Vulnerabilidades explotables hoy
367,069en 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,242
- Alto9,242
- Medio5,232
- Bajo501
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2025-27053—0.2%
——0——CVE-2025-47341—0.2%
——0——CVE-2026-559978.8 ALT0.2%
——0Rancher issues long-lived registration tokens to authenticate nodes and agents joining a downstream cluster. These tokens were stored and exposed in plaintext with no expiration, so a malicious user could obtain one either through the Rancher API, etcd, stored automation, or direct file access on a node, and could use it at any time to register a rogue node into the cluster.25dCVE-2026-27670—0.2%
——0——CVE-2023-20619—0.2%
——0——CVE-2026-642385.5 MED0.2%
——0In the Linux kernel, the following vulnerability has been resolved:
gpio: shared: fix deadlock on shared proxy's parent removal
Commit 710abda58055 ("gpio: shared: call gpio_chip::of_xlate() if set")
used the mutex embedded in struct gpio_shared_entry to protect the
offset field which now can be modified after assignment. The critical
section however is too wide and introduced a potential deadlock on the
removal of the shared GPIO proxy's parent.
Make the critical section shorter - only protect the offset when it's
being read.
While at it: mention the fact that the entry lock is now also used to
protect against concurrent access to the offset field in the structure's
documentation.18dCVE-2025-4737—0.2%
——0——CVE-2025-47353—0.2%
——0——CVE-2026-112765.1 MED0.2%
——0Inappropriate implementation in Cast in Google Chrome prior to 149.0.7827.53 allowed an attacker on the local network segment to bypass discretionary access control via malicious network traffic. (Chromium security severity: Low)39dCVE-2023-52950—0.2%
——0——CVE-2024-49738—0.2%
——0——CVE-2024-27224—0.2%
——0——CVE-2026-185912.1 BAJ0.2%
——0A vulnerability was identified in Meesho Online Shopping App up to 20260607 on Android. Affected by this vulnerability is an unknown functionality of the component com.meesho.supply. Such manipulation of the argument user_id/phone number/email address/name leads to cleartext storage of sensitive information. The attack can be executed directly on the physical device. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure.19dCVE-2026-122347.8 ALT0.2%
——0The userspace syscall verifiers z_vrfy_zsock_sendmsg() and z_vrfy_zsock_recvmsg() in subsys/net/lib/sockets/sockets.c snapshot the caller-supplied struct net_msghdr into a kernel-side copy with k_usermode_from_copy(), but then re-read the still-live user struct for subsequent decisions. The kernel iovec shadow buffer is sized from one read of msg->msg_iovlen, while the population loop is bounded by a second, live read of the same field.
Because msg points into ordinary user memory, a cooperating second thread in the same memory domain can inflate msg->msg_iovlen in the window between the sizing read and the loop test (a classic double-fetch / TOCTOU). The population loop then iterates past the number of net_iovec slots actually allocated, writing attacker-influenced iov_base/iov_len values beyond the end of the kernel-heap shadow buffer. The recvmsg verifier has the same defect on both its inbound and result write-back loops.
The code is reachable from an unprivileged user thread whenever CONFIG_USERSPACE is enabled and the zsock_sendmsg/zsock_recvmsg syscalls are available. A successful race corrupts kernel-managed heap memory across the user-to-kernel privilege boundary, yielding a local privilege-escalation primitive or, at minimum, a kernel-fault denial of service. The fix copies the header once and derives every size, bound, and gate from the snapshot, copying each iovec entry atomically so its base and length can no longer be raced apart.5dCVE-2024-53833—0.2%
——0——CVE-2026-31430—0.2%
——0——CVE-2024-40654—0.2%
——0——CVE-2019-25651—0.2%
——0——CVE-2025-48629—0.2%
——0——CVE-2026-493035.1 MED0.2%
——0Permission control vulnerability in the notification module. Impact: Successful exploitation of this vulnerability may affect availability.3dCVE-2017-13308—0.2%
——0——CVE-2026-0019—0.2%
——0——CVE-2022-48454—0.2%
——0——CVE-2026-7997—0.2%
——0——CVE-2025-47360—0.2%
——0——CVE-2026-329887.5 ALT0.2%
——0OpenClaw before 2026.3.11 contains a sandbox boundary bypass vulnerability in fs-bridge staged writes where temporary file creation and population are not pinned to a verified parent directory. Attackers can exploit a race condition in parent-path alias changes to write attacker-controlled bytes outside the intended validated path before the final guarded replace step executes.37dCVE-2026-713176.5 MED0.2%
——0Lemur manages TLS certificate creation. Prior to 1.9.3, POST /api/1/authorities with type=subca did not require AuthorityPermission on the parent authority when ADMIN_ONLY_AUTHORITY_CREATION was false. AssociatedAuthoritySchema resolved the caller-supplied parent and passed it through authority creation to cryptography-issuer, which used the parent authority_certificate.private_key to sign a new intermediate. Any authenticated non-read-only user in that supported configuration could chain a sub-CA to an internal root for which the user held no role. The resulting intermediate could issue trusted certificates and its private key could be used outside Lemur, bypassing normal issuance controls. The fix checks AuthorityPermission on every supplied parent before invoking the issuer. This issue is fixed in version 1.9.3.12dCVE-2025-47338—0.2%
——0——CVE-2025-47361—0.2%
——0——CVE-2023-42642—0.2%
——0——CVE-2024-20099—0.2%
——0——CVE-2024-53836—0.2%
——0——CVE-2025-48632—0.2%
——0——CVE-2025-20766—0.2%
——0——CVE-2026-28546—0.2%
——0——CVE-2025-20764—0.2%
——0——CVE-2025-20743—0.2%
——0——CVE-2026-23165—0.2%
——0——CVE-2026-23130—0.2%
——0——CVE-2025-6182—0.2%
——0——