Vulnerabilities exploitable today
378,631in 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,721
New KEV · 24H4
Exploit Today ≥ 701,652
Distribution · last window
- Critical2,396
- High8,640
- Medium6,936
- Low787
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2023-31249——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2023-27883——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2026-54709——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-54637. Reason: This candidate is a duplicate of CVE-2026-54637. Notes: All CVE users should reference CVE-2026-54637 instead of this candidate.78dCVE-2023-7353——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.48dCVE-2025-66334—0.0%
——0——CVE-2026-588487.0 HIG0.0%
——0In multiple functions of alloc.c, there is a possible unauthorized read/write access due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.14dCVE-2025-27570——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused41dCVE-2026-15424——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.41dCVE-2026-23591——
——0Rejected reason: Withdrawn by requester.21dCVE-2026-66789——
——0Rejected reason: This CVE ID was assigned in error as a duplicate of CVE-2026-70495, which describes the same vulnerability. Please use CVE-2026-70495 instead.7dCVE-2023-40746——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2025-20801—0.0%
——0——CVE-2026-22657——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.43dCVE-2026-69701——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.32dCVE-2023-54381——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.48dCVE-2026-29031——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.43dCVE-2023-28717——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2026-67188——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.55dCVE-2023-41959——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2026-56716——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.23dCVE-2023-38540——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2026-26349——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.43dCVE-2026-56715——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.23dCVE-2023-40149——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2026-51245——
——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.53dCVE-2026-51256——
——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.53dCVE-2026-23765——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.43dCVE-2023-32630——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2023-47214——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2026-35006——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.43dCVE-2023-46702——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2023-22289——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2026-49945——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.76dCVE-2023-42779——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2025-20020——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused41dCVE-2022-51004——
——0Rejected reason: This CVE ID has been rejected.26dCVE-2023-24543——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused26dCVE-2026-68577——
——0Rejected reason: Reserved via standalone CLI outside the OSIM flaw workflow; releasing so the CVE ID can be properly reserved and linked through OSIM when the flaw is worked.53dCVE-2026-62175——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-60091. Reason: This candidate is a duplicate of CVE-2026-60091. Notes: All CVE users should reference CVE-2026-60091 instead of this candidate.69dCVE-2026-45220——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.14d