Vulnerabilities exploitable today
365,446in 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,682
New KEV · 24H0
Exploit Today ≥ 701,626
Distribution · last window
- Critical2,337
- High9,994
- Medium4,918
- Low461
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-51301——
——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.27dCVE-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.43dCVE-2023-54378——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.22dCVE-2026-62177——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-60085. Reason: This candidate is a duplicate of CVE-2026-60085. Notes: All CVE users should reference CVE-2026-60085 instead of this candidate.43dCVE-2026-29026——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.17dCVE-2023-54387——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.22dCVE-2025-596106.4 MED0.0%
——0Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer.36dCVE-2026-35027——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.17dCVE-2026-51258——
——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.27dCVE-2026-61841——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-61449. Reason: This candidate is a duplicate of CVE-2026-61449. Notes: All CVE users should reference CVE-2026-61449 instead of this candidate.43dCVE-2026-14170——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.30dCVE-2025-32737——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused15dCVE-2025-35977——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused15dCVE-2023-54380——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.22dCVE-2026-70623——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.20dCVE-2025-30178——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused15dCVE-2021-47991——
——0Rejected reason: This CVE ID has been rejected.16dCVE-2023-54375——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.22dCVE-2026-58212——
——0Rejected reason: Further research determined the issue is not a vulnerability based on CNA Rule 4.1.12 The act of updating Product dependencies MUST NOT be determined to be a Vulnerability, regardless of whether the dependencies have Vulnerabilities.50dCVE-2023-54381——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.22dCVE-2025-27076—0.0%
——0——CVE-2026-29010——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.17dCVE-2023-54382——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.22dCVE-2023-54384——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.22dCVE-2023-54385——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.22dCVE-2026-24438——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.17dCVE-2023-7344——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.6dCVE-2026-35006——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.17dCVE-2025-66333—0.0%
——0——CVE-2026-11427——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.6dCVE-2026-56875——
——0Rejected reason: reserved but not needed6dCVE-2026-35026——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.17dCVE-2021-47992——
——0Rejected reason: This CVE ID has been rejected.16dCVE-2026-76831——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.3dCVE-2026-28184——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.13dCVE-2026-51242——
——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.27dCVE-2026-6889——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.27dCVE-2026-58461——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.44dCVE-2026-76829——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.3dCVE-2026-29028——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.17d