Vulnerabilities exploitable today
367,144in 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,256
- High9,258
- Medium5,266
- Low507
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2024-41591—17.0%
——5——CVE-2020-36943—17.0%
——5——CVE-2025-47449—17.0%
——5——CVE-2024-31902—17.0%
——5——CVE-2022-23957—17.0%
——5——CVE-2022-49676—17.0%
——5——CVE-2025-14542—17.0%
——5——CVE-2021-47654—17.0%
——5——CVE-2022-49473—17.0%
——5——CVE-2022-32881—17.0%
——5——CVE-2026-644418.8 HIG17.0%
——5In the Linux kernel, the following vulnerability has been resolved:
staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr()
Three IE/attribute parsing functions have missing bounds checks.
rtw_get_sec_ie() and rtw_get_wapi_ie() iterate over a raw IE buffer
without verifying that the header bytes (tag + length) are within the
remaining buffer before reading them. Additionally, rtw_get_sec_ie()
compares the 4-byte WPA OUI at cnt+2 without checking that at least
6 bytes remain, and rtw_get_wapi_ie() compares a 4-byte WAPI OUI at
cnt+6 without checking that at least 10 bytes remain.
rtw_get_wps_attr() reads wps_ie[0] and wps_ie+2 unconditionally at
entry, before verifying that wps_ielen is large enough to contain
the 6-byte WPS IE header (element_id + length + 4-byte OUI). Inside
the attribute loop, get_unaligned_be16() is called on attr_ptr and
attr_ptr+2 without checking that 4 bytes remain in the buffer.
Add a cnt+2 bounds check before each loop body in rtw_get_sec_ie()
and rtw_get_wapi_ie(), guard each multi-byte comparison with a minimum
IE length requirement, add a wps_ielen < 6 early return in
rtw_get_wps_attr(), and add a 4-byte bounds check in its inner loop.14dCVE-2026-668326.5 MED17.0%
——5When the Mira Android app opens in-app WebView content (e.g., shop redirect flows), the user's live session token is appended to the URL as a query string parameter, and a persistent user identifier is included in the WebView's User-Agent header. Both are then transmitted to third-party web properties, referrer logs, and any JavaScript running in the WebView context.19dCVE-2025-6531—17.0%
——5——CVE-2022-49211—17.0%
——5——CVE-2025-25017—17.0%
——5——CVE-2021-22276—17.0%
——5——CVE-2022-49512—17.0%
——5——CVE-2022-23953—17.0%
——5——CVE-2026-43176—17.0%
——5——CVE-2022-23958—17.0%
——5——CVE-2022-49366—17.0%
——5——CVE-2021-47322—17.0%
——5——CVE-2022-40180—17.0%
——5——CVE-2025-0329—17.0%
——5——CVE-2026-1283—17.0%
——5——CVE-2023-42924—17.0%
——5——CVE-2025-11839—17.0%
——5——CVE-2022-49569—17.0%
——5——CVE-2019-20459—17.0%
——5——CVE-2023-22345—17.0%
——5——CVE-2026-3206—17.0%
——5——CVE-2022-49284—17.0%
——5——CVE-2025-11840—17.0%
——5——CVE-2022-50942—17.0%
——5——CVE-2025-27616—17.0%
——5——CVE-2022-49386—17.0%
——5——CVE-2026-32138—17.0%
——5——CVE-2024-49208—17.0%
——5——CVE-2022-49147—17.0%
——5——CVE-2025-11932—17.0%
——5——