Vulnerabilities exploitable today
349,489in 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,647
New KEV · 24H0
Exploit Today ≥ 701,582
Distribution · last window
- Critical1,331
- High4,356
- Medium3,715
- Low289
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2021-39769—1.0%
——0——CVE-2026-0020—1.0%
——0——CVE-2022-26464—1.0%
——0——CVE-2021-39779—1.0%
——0——CVE-2021-1033—1.0%
——0——CVE-2025-33088—1.0%
——0——CVE-2026-127056.4 MED1.0%
——0Missing support for integrity check vulnerability in ABB KNX Update Tool (ABB), ABB KNX Update Tool (BJE).
This issue affects KNX Update Tool (ABB): through 2.0.175; KNX Update Tool (BJE): through 2.0.175.1dCVE-2026-02383.2 LOW1.0%
——0A vulnerability in Palo Alto Networks Broker VM allows an authenticated administrator to inject arbitrary content into certain Broker VM fields.5dCVE-2025-54633—1.0%
——0——CVE-2021-39770—1.0%
——0——CVE-2024-38414—1.0%
——0——CVE-2022-20129—1.0%
——0——CVE-2023-20602—1.0%
——0——CVE-2024-38411—1.0%
——0——CVE-2023-20604—1.0%
——0——CVE-2022-26457—1.0%
——0——CVE-2026-0021—1.0%
——0——CVE-2023-21159—1.0%
——0——CVE-2025-48615—1.0%
——0——CVE-2023-20906—1.0%
——0——CVE-2022-49884—1.0%
——0——CVE-2026-532075.5 MED1.0%
——0In the Linux kernel, the following vulnerability has been resolved:
mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison
Two concurrent madvise(MADV_HWPOISON) calls on the same hugetlb page can
trigger a recursive spinlock self-deadlock (AA deadlock) on hugetlb_lock
when racing with a concurrent unmap:
thread#0 thread#1
-------- --------
madvise(folio, MADV_HWPOISON)
-> poisons the folio successfully
madvise(folio, MADV_HWPOISON) unmap(folio)
try_memory_failure_hugetlb
get_huge_page_for_hwpoison
spin_lock_irq(&hugetlb_lock) <- held
__get_huge_page_for_hwpoison
hugetlb_update_hwpoison()
-> MF_HUGETLB_FOLIO_PRE_POISONED
goto out:
folio_put()
refcount: 1 -> 0
free_huge_folio()
spin_lock_irqsave(&hugetlb_lock)
-> AA DEADLOCK!
The out: path in __get_huge_page_for_hwpoison() calls folio_put() to drop
the GUP reference while the hugetlb_lock is still held by the hugetlb.c
wrapper get_huge_page_for_hwpoison(). If concurrent unmap has released
the page table mapping reference, folio_put() drops the folio refcount to
zero, triggering free_huge_folio() which attempts to re-acquire the
non-recursive hugetlb_lock.
Fix this by moving hugetlb_lock acquisition from the hugetlb.c wrapper
into get_huge_page_for_hwpoison(). Place spin_unlock_irq() before the
folio_put() at the out: label so the folio is always released outside the
lock.
[akpm@linux-foundation.org: fix race, rename label per Miaohe]16dCVE-2026-42481—1.0%
——0——CVE-2025-53919—1.0%
——0——CVE-2025-52608—0.9%
——0——CVE-2023-21236—1.0%
——0——CVE-2022-20143—1.0%
——0——CVE-2026-43433—1.0%
——0——CVE-2024-43063—1.0%
——0——CVE-2025-48654—1.0%
——0——CVE-2023-33891—1.0%
——0——CVE-2025-48612—1.0%
——0——CVE-2023-33892—1.0%
——0——CVE-2024-22010—1.0%
——0——CVE-2025-52937—1.0%
——0——CVE-2025-39884—1.0%
——0——CVE-2026-452226.1 MED1.0%
——0Summarize versions through 0.14.1, fixed in commit 0cfb0fb, creates the daemon configuration directory and file with default filesystem permissions that may be world-readable on Unix-like systems, allowing local attackers to read bearer tokens and API credentials stored in ~/.summarize/daemon.json. A local attacker can exploit these permissive permissions to read the daemon bearer token and persisted provider credentials, enabling unauthorized access to the daemon or recovery of sensitive API keys.4dCVE-2026-415162.5 LOW1.0%
——0OP-TEE is a Trusted Execution Environment (TEE) designed as companion to a non-secure Linux kernel running on Arm; Cortex-A cores using the TrustZone technology. Starting in version 4.5.0 and prior to version 4.11.0, the RSA PKCS#1 v1.5 decryption implementation in the Hisilicon HPRE crypto driver uses non-constant-time `memcmp()` for label hash verification and has multiple distinguishable error paths. This creates a Bleichenbacher-style padding oracle that allows an attacker to recover RSA PKCS#1 v1.5 plaintext. Version 4.11.0 contains a patch. As a workaround, disable Hisilicon HPRE RSA driver with `CFG_HISILICON_ACC_V3=n`.11dCVE-2026-56409—1.0%
——0——CVE-2022-26460—1.0%
——0——