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,446
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-34371——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2017-1821——
——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-34465——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34466——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34470——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2023-27883——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused55dCVE-2025-34471——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34405——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34415——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34426——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34431——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34432——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34473——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34474——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34475——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34476——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-58419——
——0Rejected reason: Not used4dCVE-2025-34477——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34478——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34479——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34480——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2026-25698——
——0Rejected reason: Not used4dCVE-2025-34542——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-67607——
——0Rejected reason: Not used4dCVE-2025-34547——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34548——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34549——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34534——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2025-34538——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.4dCVE-2026-105391——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.3dCVE-2017-4115——
——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-2017-4116——
——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-2017-4229——
——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-2024-8674——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2016-7702——
——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: none4dCVE-2016-8186——
——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: none4dCVE-2026-35006——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2016-10353——
——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: none4dCVE-2026-24336——
——0Rejected reason: Not used4dCVE-2026-977325.1 MED0.0%
——0IRONMACE Ironshield 1.0.0.167 has a tvk.sys kernel-mode driver that authenticates client executables by checking for expected publisher and root-certificate strings in WIN_CERTIFICATE data ("IRONMACE Co., Ltd." and "DigiCert Trusted Root G4") instead of parsing and validating the PKCS signature data. As a result, a local unprivileged attacker may bypass this via crafted certificate data and obtain access to privileged IOCTL functionality.26d