Vulnerabilities exploitable today
354,835in current view
Single score combining CVSS, KEV membership and EPSS. Every CVE with its own record — timeline from publication to active exploitation.
In KEV catalog1,656
New KEV · 24H0
Exploit Today ≥ 701,601
Distribution · last window
- Critical2,555
- High9,167
- Medium7,427
- Low691
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-46547—5.9%
——2——CVE-2024-23591—5.9%
——2——CVE-2026-593284.2 MED5.9%
——2Spring Tools for Eclipse renders Spring Boot starter wizard dependency tooltips in a native embedded browser (SWT Browser) with JavaScript enabled. Using untrusted and compromised Initializr endpoints for the Spring Boot starter wizard can result in arbitrary script execution inside the embedded browser when a developer hovers a dependency checkbox in the New Spring Starter Project wizard. Impact is limited to in-IDE UI spoofing and outbound network beaconing rather than full code execution.
Affected Spring Products and Versions:
Spring Tools for Eclipse: 5.2.0 and earlier3dCVE-2026-664168.8 HIG5.9%
——2Leantime 3.6.2 contains a cross-site request forgery vulnerability that allows unauthenticated attackers to perform state-changing actions on behalf of authenticated users by excluding the Laravel VerifyCsrfToken middleware from the global middleware stack in app/Http/Kernel.php. Attackers can craft malicious pages delivered via phishing emails or malicious websites to trigger unauthorized POST, PUT, and DELETE requests that create or delete projects, modify settings, and change permissions as any authenticated user.1dCVE-2026-12779—5.9%
——2——CVE-2024-32998—5.9%
——2——CVE-2026-8369—5.9%
——2——CVE-2025-58174—5.9%
——2——CVE-2022-47376—5.9%
——2——CVE-2025-64707—5.9%
——2——CVE-2025-8102—5.9%
——2——CVE-2023-38721—5.9%
——2——CVE-2023-44292—5.9%
——2——CVE-2025-68353—5.9%
——2——CVE-2023-45702—5.9%
——2——CVE-2018-9457—5.9%
——2——CVE-2025-39684—5.9%
——2——CVE-2024-56706—5.9%
——2——CVE-2023-25604—5.9%
——2——CVE-2025-68977—5.9%
——2——CVE-2023-54325—5.9%
——2——CVE-2025-70094—5.9%
——2——CVE-2025-6183—5.9%
——2——CVE-2026-5321—5.9%
——2——CVE-2023-42969—5.9%
——2——CVE-2025-38347—5.9%
——2——CVE-2025-67637—5.9%
——2——CVE-2018-11910—5.9%
——2——CVE-2025-41063—5.9%
——2——CVE-2026-64192—5.9%
——2In the Linux kernel, the following vulnerability has been resolved:
bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized
When CONFIG_BPF_LSM=y is set, BPF inode storage maps
(BPF_MAP_TYPE_INODE_STORAGE) are compiled into the kernel. However,
if the BPF LSM is not explicitly enabled at boot time (e.g. omitted
from the "lsm=" boot parameter), lsm_prepare() is never executed for
the BPF LSM.
Consequently, the BPF inode security blob offset
(bpf_lsm_blob_sizes.lbs_inode) is never initialized and remains at
its default compiled size of 8 bytes instead of being updated to a
valid offset past the reserved struct rcu_head (typically 16 bytes
or more).
When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGE
map, bpf_inode() evaluates inode->i_security + 8. This erroneously
aliases the struct rcu_head.func callback pointer at the beginning
of the inode->i_security blob. During subsequent map element cleanup
or inode destruction, writing NULL to owner_storage clears the queued
RCU callback pointer. When rcu_do_batch() later executes the queued
callback, it attempts an instruction fetch at address 0x0, triggering
an immediate kernel panic.
Fix this by introducing a global bpf_lsm_initialized boolean flag
marked with __ro_after_init. Set this flag to true inside bpf_lsm_init()
when the LSM framework successfully registers the BPF LSM. Gate map
allocation in inode_storage_map_alloc() on this flag, returning
-EOPNOTSUPP if the BPF LSM is in turn uninitialized.
This fail-fast approach prevents userspace from allocating inode
storage maps when the supporting BPF LSM infrastructure is absent,
avoiding zombie map states.3dCVE-2024-34671—5.9%
——2——CVE-2018-11909—5.9%
——2——CVE-2023-40103—5.9%
——2——CVE-2021-30295—5.9%
——2——CVE-2025-6214—5.9%
——2——CVE-2026-129826.1 MED5.9%
——2The Document Gallery WordPress plugin before 5.1.1 does not properly sanitise and escape user input before reflecting it back in the response of an unauthenticated AJAX action, leading to a Reflected Cross-Site Scripting vulnerability which can be exploited against unauthenticated users.6dCVE-2025-64329—5.9%
——2——CVE-2025-70091—5.9%
——2——CVE-2026-1094—5.9%
——2——CVE-2024-27367—5.9%
——2——