Vulnerabilities exploitable today
401,031in 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,748
New KEV · 24H0
Exploit Today ≥ 701,665
Distribution · last window
- Critical3,503
- High15,971
- Medium14,886
- Low1,471
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-34485——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2025-34486——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2024-8677——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2026-49945——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2025-34472——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2026-62164——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-60087. Reason: This candidate is a duplicate of CVE-2026-60087. Notes: All CVE users should reference CVE-2026-60087 instead of this candidate.98dCVE-2023-47538——
——0Rejected reason: Not used3dCVE-2017-1891——
——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: none3dCVE-2025-59924——
——0Rejected reason: Not used3dCVE-2025-9197——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2025-34296——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2026-9611——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.82dCVE-2026-108117——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.2dCVE-2025-34321——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2016-7756——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2016. Notes: none3dCVE-2026-107772——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.2dCVE-2026-107345——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.2dCVE-2026-107274——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.2dCVE-2025-34250——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2025-34268——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2025-34275——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2025-34276——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2025-34279——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2025-34488——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2025-34285——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2026-58125——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2023-22423——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused55dCVE-2026-78304——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2025-473446.7 MED0.0%
——0Memory corruption while handling sensor utility operations.14dCVE-2025-34492——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2023-39931——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused55dCVE-2026-252636.6 MED0.0%
——0Memory corruption while processing IOCTL command called from user space to the kernel with invalid parameters.12dCVE-2016-9058——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2016. Notes: none3dCVE-2025-34325——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2025-34326——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2025-34327——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2023-54375——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.76dCVE-2026-51253——
——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-2025-34338——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.3dCVE-2026-49118——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.4d