Vulnerabilities exploitable today
352,162in 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
- Critical2,073
- High6,924
- Medium5,904
- Low547
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2021-0467—2.7%
——1——CVE-2025-59892—2.7%
——1——CVE-2025-58801—2.7%
——1——CVE-2024-22313—2.7%
——1——CVE-2025-28981—2.7%
——1——CVE-2026-604497.1 HIG2.7%
——1Vulnerability in the Oracle WebCenter Content product of Oracle Fusion Middleware (component: Content Server). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle WebCenter Content executes to compromise Oracle WebCenter Content. While the vulnerability is in Oracle WebCenter Content, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle WebCenter Content accessible data. CVSS 3.1 Base Score 7.1 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).2dCVE-2026-48693—2.7%
——1——CVE-2026-24988—2.7%
——1——CVE-2025-46512—2.7%
——1——CVE-2026-638177.8 HIG2.7%
——1In the Linux kernel, the following vulnerability has been resolved:
f2fs: validate compress cache inode only when enabled
F2FS_COMPRESS_INO() uses NM_I(sbi)->max_nid as the synthetic inode
number for the compressed page cache inode. That inode only exists when
the compress_cache mount option is enabled.
When compress_cache is disabled, max_nid is outside the valid inode
range. A corrupted directory entry that points to ino == max_nid should
therefore be rejected by f2fs_check_nid_range(). However, is_meta_ino()
currently treats F2FS_COMPRESS_INO() as a meta inode unconditionally,
so f2fs_iget() bypasses do_read_inode() and its nid range check, and
instantiates a fake internal inode instead.
Gate the compressed cache inode case on COMPRESS_CACHE, matching
f2fs_init_compress_inode(). With compress_cache disabled, ino ==
max_nid now follows the normal inode path and is rejected as an
out-of-range nid.3dCVE-2026-411242.3 LOW2.7%
——1Dell PowerProtect Data Domain, versions 7.7.1.0 through 8.6, LTS2026 release version 8.6.1.0 through 8.6.1.10, LTS2025 release version 8.3.1.0 through 8.3.1.30, LTS2024 release versions 7.13.1.0 through 7.13.1.70 contain an Improper limitation of a pathname to a restricted directory ('path traversal') vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Information exposure.15dCVE-2025-62125—2.7%
——1——CVE-2025-48382—2.7%
——1——CVE-2025-20048—2.7%
——1——CVE-2024-8011—2.7%
——1——CVE-2026-1087—2.7%
——1——CVE-2023-40097—2.7%
——1——CVE-2026-1086—2.7%
——1——CVE-2025-20017—2.7%
——1——CVE-2026-45981—2.7%
——1——CVE-2020-0497—2.7%
——1——CVE-2026-532867.8 HIG2.7%
——1In the Linux kernel, the following vulnerability has been resolved:
idpf: fix double free and use-after-free in aux device error paths
When auxiliary_device_add() fails in idpf_plug_vport_aux_dev() or
idpf_plug_core_aux_dev(), the err_aux_dev_add label calls
auxiliary_device_uninit() and falls through to err_aux_dev_init. The
uninit call will trigger put_device(), which invokes the release
callback (idpf_vport_adev_release / idpf_core_adev_release) that frees
iadev. The fall-through then reads adev->id from the freed iadev for
ida_free() and double-frees iadev with kfree().
Free the IDA slot and clear the back-pointer before uninit, while adev
is still valid, then return immediately.
Commit 65637c3a1811 ("idpf: fix UAF in RDMA core aux dev deinitialization")
fixed the same use-after-free in the matching unplug path in this file but
missed both probe error paths.16dCVE-2025-71285—2.7%
——1——CVE-2026-453289.3 CRI2.7%
——1ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.5.4 and 6.0, the esp_tee component exposes secure-service wrappers in esp_secure_services.c and esp_secure_services_iram.c that bridge calls from the user application (i.e. the REE) to TEE-protected hardware peripherals (AES, SHA, ECC, HMAC, SPI, MMU, WDT) and to the security feature like attestation, OTA updates, secure storage. This issue has been patched in versions 5.5.5 and 6.0.1.7hCVE-2025-13131—2.7%
——1——CVE-2018-25273—2.7%
——1——CVE-2026-3589—2.7%
——1——CVE-2026-43449—2.7%
——1——CVE-2024-23460—2.7%
——1——CVE-2026-1464—2.7%
——1——CVE-2026-23180—2.7%
——1——CVE-2026-1073—2.7%
——1——CVE-2026-43195—2.7%
——1——CVE-2025-30756—2.7%
——1——CVE-2025-5345—2.7%
——1——CVE-2026-41965—2.7%
——1——CVE-2025-37127—2.7%
——1——CVE-2026-42250—2.7%
——1——CVE-2025-43274—2.7%
——1——CVE-2026-46182—2.7%
——1——