Vulnerabilities exploitable today
377,415in 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,716
New KEV · 24H3
Exploit Today ≥ 701,647
Distribution · last window
- Critical2,355
- High8,510
- Medium6,633
- Low715
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-10149——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.3dCVE-2023-34084——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused22dCVE-2026-0121—0.0%
——0——CVE-2026-35026——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.39dCVE-2026-61605——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-58655. Reason: This candidate is a duplicate of CVE-2026-58655. Notes: All CVE users should reference CVE-2026-58655 instead of this candidate.65dCVE-2026-29011——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.39dCVE-2026-51240——
——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.49dCVE-2025-13398——
——0Rejected reason: This CVE ID is a duplicate of CVE-2025-13542 and was never published. Both IDs were assigned to the same unauthenticated privilege escalation vulnerability in the DesignThemes LMS WordPress plugin. All CVE users should reference CVE-2025-13542 instead of this ID.16dCVE-2026-85789——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.2dCVE-2026-58461——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.66dCVE-2025-25275——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused37dCVE-2026-6822——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.29dCVE-2020-37259——
——0Rejected reason: This CVE ID has been rejected.38dCVE-2026-11902——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.28dCVE-2023-40746——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused22dCVE-2026-6890——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.50dCVE-2026-49153——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.10dCVE-2026-29025——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.39dCVE-2026-14170——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.52dCVE-2026-46535——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.29dCVE-2026-76829——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.25dCVE-2023-42779——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused22dCVE-2023-49592——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused22dCVE-2026-71982——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.25dCVE-2026-22651——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.39dCVE-2026-28184——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.36dCVE-2026-51279——
——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.49dCVE-2026-51249——
——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.49dCVE-2026-26348——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.39dCVE-2026-10145——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.3dCVE-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.65dCVE-2026-11740——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.64dCVE-2026-29010——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.39dCVE-2026-47105——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.80dCVE-2023-54372——
——0Rejected reason: This CVE ID has been rejected.38dCVE-2013-1446——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Was assigned for an old issue in the brltty daemon and never published completely.4dCVE-2026-51287——
——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.49dCVE-2026-74226——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.30dCVE-2026-569148.4 HIG0.0%
——0In multiple locations, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.2dCVE-2023-54381——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.44d