Vulnerabilities exploitable today
366,836in 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,685
New KEV · 24H0
Exploit Today ≥ 701,629
Distribution · last window
- Critical2,374
- High9,658
- Medium5,454
- Low526
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2021-33130—15.9%
——5——CVE-2026-26464—15.9%
——5——CVE-2023-51454—15.9%
——5——CVE-2026-40462—15.9%
——5——CVE-2024-47392—15.9%
——5——CVE-2025-7706—15.9%
——5——CVE-2023-37996—15.9%
——5——CVE-2024-47366—15.9%
——5——CVE-2025-36093—15.9%
——5——CVE-2024-47625—15.9%
——5——CVE-2024-10310—15.9%
——5——CVE-2025-43745—15.9%
——5——CVE-2026-456748.7 HIG15.9%
——5Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty's DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses. Versions 4.1.135.Final and 4.2.15.Final patch the issue.8dCVE-2025-9565—15.9%
——5——CVE-2024-47357—15.9%
——5——CVE-2021-40989—15.9%
——5——CVE-2026-44471—15.9%
——5——CVE-2020-7123—15.9%
——5——CVE-2024-40455—15.9%
——5——CVE-2025-40886—15.9%
——5——CVE-2025-63563—15.9%
——5——CVE-2026-132678.1 HIG15.9%
——5IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 and IBM Verify Identity Access Container 11.0 through 11.0.3 could allow an authenticated user to gain privileges of another user via a specially crafted request.12dCVE-2025-1749—15.9%
——5——CVE-2021-476455.5 MED15.9%
——5In the Linux kernel, the following vulnerability has been resolved:
media: staging: media: zoran: calculate the right buffer number for zoran_reap_stat_com
On the case tmp_dcim=1, the index of buffer is miscalculated.
This generate a NULL pointer dereference later.
So let's fix the calcul and add a check to prevent this to reappear.18dCVE-2026-762586.5 MED15.9%
——5In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.10, 3.9.24, and 3.8.71, a user who does not hold the "admin" or "power" Splunk roles could register an arbitrary companion app and cause Splunk Secure Gateway to forward mobile user requests, including tokens that compromise all relevant data available to the affected mobile user, to an attacker-controlled Uniform Resource Locator (URL). The vulnerability is possible because a hard-coded cryptographic key in the Splunk Secure Gateway companion app registration handler allows for arbitrary callback URL registration without restriction. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.9dCVE-2026-22753—15.9%
——5——CVE-2026-194176.5 MED15.9%
——5The KiviCare WordPress plugin before 4.5.4 does not verify that the requesting user is entitled to the media file being served, allowing authenticated patient-level users to download any file in the media library, including other patients' uploaded medical reports.10dCVE-2024-7998—15.9%
——5——CVE-2025-69239—15.9%
——5——CVE-2022-4938—15.9%
——5——CVE-2025-61676—15.9%
——5——CVE-2025-14361—15.9%
——5——CVE-2025-11087—15.9%
——5——CVE-2025-63830—15.9%
——5——CVE-2024-501417.8 HIG15.9%
——5In the Linux kernel, the following vulnerability has been resolved:
ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context
PRMT needs to find the correct type of block to translate the PA-VA
mapping for EFI runtime services.
The issue arises because the PRMT is finding a block of type
EFI_CONVENTIONAL_MEMORY, which is not appropriate for runtime services
as described in Section 2.2.2 (Runtime Services) of the UEFI
Specification [1]. Since the PRM handler is a type of runtime service,
this causes an exception when the PRM handler is called.
[Firmware Bug]: Unable to handle paging request in EFI runtime service
WARNING: CPU: 22 PID: 4330 at drivers/firmware/efi/runtime-wrappers.c:341
__efi_queue_work+0x11c/0x170
Call trace:
Let PRMT find a block with EFI_MEMORY_RUNTIME for PRM handler and PRM
context.
If no suitable block is found, a warning message will be printed, but
the procedure continues to manage the next PRM handler.
However, if the PRM handler is actually called without proper allocation,
it would result in a failure during error handling.
By using the correct memory types for runtime services, ensure that the
PRM handler and the context are properly mapped in the virtual address
space during runtime, preventing the paging request error.
The issue is really that only memory that has been remapped for runtime
by the firmware can be used by the PRM handler, and so the region needs
to have the EFI_MEMORY_RUNTIME attribute.
[ rjw: Subject and changelog edits ]25dCVE-2026-28284—15.9%
——5——CVE-2022-49097—15.9%
——5——CVE-2022-49091—15.9%
——5——CVE-2026-4331—15.9%
——5——CVE-2021-47766—15.9%
——5——