Vulnerabilities exploitable today
401,106in 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,754
New KEV · 24H0
Exploit Today ≥ 701,665
Distribution · last window
- Critical3,441
- High15,704
- Medium14,721
- Low1,447
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2017-2016——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none4dCVE-2025-35000——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34932——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34931——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34896——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-35001——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-35002——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2026-57513——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.2dCVE-2025-34897——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34898——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34899——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34900——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-39751——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2025-59670——
——0Rejected reason: Not used4dCVE-2025-34901——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34902——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34903——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34904——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-61847——
——0Rejected reason: Not used4dCVE-2024-56786——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2025-34905——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34930——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34906——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-67315——
——0Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.2dCVE-2025-34907——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34908——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34909——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34910——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34916——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34929——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34928——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-69290——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2025. Notes: none2dCVE-2025-34917——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-21630——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2024-53689——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2026-51255——
——0Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.82dCVE-2024-5996——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2025-34792——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34980——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2dCVE-2025-34793——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.2d