Vulnerabilities exploitable today
349,427in 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,327
- High4,319
- Medium3,685
- Low289
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2020-14092—99.8%
——30——CVE-2014-0515—99.8%
——30——CVE-2024-21650—99.8%
——30——CVE-2016-7552—99.8%
——30——CVE-2022-3562—99.8%
——30——CVE-2024-31309—99.8%
——30——CVE-2021-2190—99.8%
——30——CVE-2023-0992—99.8%
——30——CVE-2012-1425—99.8%
——30——CVE-2024-7120—99.8%
——30——CVE-2013-2248—99.8%
——30——CVE-2023-48795—99.8%
——30——CVE-2016-4010—99.8%
——30——CVE-2021-46422—99.8%
——30——CVE-2010-3964—99.8%
——30——CVE-2026-432848.8 HIG99.8%
——30In the Linux kernel, the following vulnerability has been resolved:
xfrm: esp: avoid in-place decrypt on shared skb frags
MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP
marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(),
so later paths that may modify packet data can first make a private
copy. The IPv4/IPv6 datagram append paths did not set this flag when
splicing pages into UDP skbs.
That leaves an ESP-in-UDP packet made from shared pipe pages looking
like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW
fast path for uncloned skbs without a frag_list and decrypts in place
over data that is not owned privately by the skb.
Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching
TCP. Also make ESP input fall back to skb_cow_data() when the flag is
present, so ESP does not decrypt externally backed frags in place.
Private nonlinear skb frags still use the existing fast path.
This intentionally does not change ESP output. In esp_output_head(),
the path that appends the ESP trailer to existing skb tailroom without
calling skb_cow_data() is not reachable for nonlinear skbs:
skb_tailroom() returns zero when skb->data_len is nonzero, while ESP
tailen is positive. Thus ESP output will either use the separate
destination-frag path or fall back to skb_cow_data().3dCVE-2024-45507—99.8%
——30——CVE-2018-3245—99.8%
——30——CVE-2022-29535—99.8%
——30——CVE-2013-1965—99.8%
——30——CVE-2015-5371—99.8%
——30——CVE-2021-31474—99.8%
——30——CVE-2012-1460—99.8%
——30——CVE-2019-7276—99.8%
——30——CVE-2021-20080—99.8%
——30——CVE-2020-24186—99.8%
——30——CVE-2019-10173—99.8%
——30——CVE-2018-11784—99.8%
——30——CVE-2023-44443—99.8%
——30——CVE-2024-27956—99.8%
——30——CVE-2016-3081—99.8%
——30——CVE-2022-4067—99.8%
——30——CVE-2021-27850—99.8%
——30——CVE-2023-30258—99.8%
——30——CVE-2002-0840—99.8%
——30——CVE-2024-22024—99.8%
——30——CVE-2005-1983—99.8%
——30——CVE-2023-24941—99.8%
——30——CVE-2020-17506—99.8%
——30——CVE-2010-0425—99.8%
——30——