Vulnerabilities exploitable today
351,920in 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,653
New KEV · 24H0
Exploit Today ≥ 701,590
Distribution · last window
- Critical1,901
- High6,163
- Medium4,997
- Low479
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-23221—2.3%
——1——CVE-2026-23229—2.3%
——1——CVE-2019-20575—2.3%
——1——CVE-2026-00978.0 HIG2.3%
——1In multiple locations, there is a possible way to bypass user interaction when pairing an LE device due to a logic error. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.7hCVE-2020-37252—2.3%
——1——CVE-2025-22886—2.3%
——1——CVE-2024-23375—2.3%
——1——CVE-2026-6369—2.3%
——1——CVE-2021-1019—2.3%
——1——CVE-2021-25416—2.3%
——1——CVE-2025-13142—2.3%
——1——CVE-2025-67499—2.3%
——1——CVE-2025-13703—2.3%
——1——CVE-2023-40098—2.3%
——1——CVE-2026-27258—2.3%
——1——CVE-2025-38674—2.3%
——1——CVE-2025-27241—2.3%
——1——CVE-2026-23275—2.3%
——1——CVE-2025-20099—2.3%
——1——CVE-2021-47898—2.3%
——1——CVE-2025-12173—2.3%
——1——CVE-2026-46076—2.3%
——1——CVE-2026-149616.2 MED2.3%
——1Pegatron `Tdelo64.sys` exposes a privileged device interface, `\\.\TdeIo`, that fails to properly restrict access to sensitive IOCTL functionality. The driver's IOCTL dispatcher does not validate caller privileges or verify user-supplied kernel memory addresses before performing memory operations. By sending crafted requests to IOCTL, a local attacker can achieve arbitrary kernel memory read and write operations, leading to privilege escalation to `NT AUTHORITY\SYSTEM`, security product bypass, credential theft, or complete system compromise.7dCVE-2026-8008—2.3%
——1——CVE-2026-462485.5 MED2.3%
——1In the Linux kernel, the following vulnerability has been resolved:
wifi: ath12k: clear stale link mapping of ahvif->links_map
When an arvif is initialized in non-AP STA mode but MLO connection
preparation fails before the arvif is created
(arvif->is_created remains false), the error path attempts to delete all
links. However, link deletion only executes when arvif->is_created is true.
As a result, ahvif retains a stale entry of arvif that is initialized but
not created.
When a new arvif is initialized with the same link id, this stale mapping
triggers the following WARN_ON.
WARNING: drivers/net/wireless/ath/ath12k/mac.c:4271 at ath12k_mac_op_change_vif_links+0x140/0x180 [ath12k], CPU#3: wpa_supplicant/275
Call trace:
ath12k_mac_op_change_vif_links+0x140/0x180 [ath12k] (P)
drv_change_vif_links+0xbc/0x1a4 [mac80211]
ieee80211_vif_update_links+0x54c/0x6a0 [mac80211]
ieee80211_vif_set_links+0x40/0x70 [mac80211]
ieee80211_prep_connection+0x84/0x450 [mac80211]
ieee80211_mgd_auth+0x200/0x480 [mac80211]
ieee80211_auth+0x14/0x20 [mac80211]
cfg80211_mlme_auth+0x90/0xf0 [cfg80211]
nl80211_authenticate+0x32c/0x380 [cfg80211]
genl_family_rcv_msg_doit+0xc8/0x134
Fix this issue by unassigning the link vif and clearing ahvif->links_map
if arvif is only initialized but not created.
Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.5-01651-QCAHKSWPL_SILICONZ-14hCVE-2026-613031.9 LOW2.3%
——1Vulnerability in the Oracle EDI Gateway product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where Oracle EDI Gateway executes to compromise Oracle EDI Gateway. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle EDI Gateway accessible data. CVSS 3.1 Base Score 1.9 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N).5hCVE-2026-529445.5 MED2.3%
——1In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE
FSCTL_SET_SPARSE in fsctl_set_sparse() modifies the file's sparse
attribute and saves it through xattr without any permission checks.
This exposes two issues:
1) A client on a read-only share can change the sparse attribute
on files it opened, even though the share is read-only.
Other FSCTL write operations already check
test_tree_conn_flag(work->tcon, KSMBD_TREE_CONN_FLAG_WRITABLE),
but FSCTL_SET_SPARSE does not.
2) Even on writable shares, clients without FILE_WRITE_DATA or
FILE_WRITE_ATTRIBUTES access should not modify the sparse
attribute. Similar handle-level checks exist in other functions
but are missing here.
Add both share-level writable check and per-handle access check.
Use goto out on error to avoid leaking file references.14dCVE-2025-10930—2.3%
——1——CVE-2026-11157—2.3%
——1——CVE-2026-33779—2.3%
——1——CVE-2021-27901—2.3%
——1——CVE-2025-24165—2.3%
——1——CVE-2025-20729—2.3%
——1——CVE-2024-1224—2.3%
——1——CVE-2026-23386—2.3%
——1——CVE-2025-38171—2.3%
——1——CVE-2025-25218—2.3%
——1——CVE-2025-633963.3 LOW2.3%
——1An issue was discovered in PyTorch v2.5 and v2.7.1. Omission of profiler.stop() can cause torch.profiler.profile (PythonTracer) to crash or hang during finalization, leading to a Denial of Service (DoS).18dCVE-2025-43991—2.3%
——1——CVE-2025-13453—2.3%
——1——