Vulnerabilities exploitable today
379,124in 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 · 24H0
Exploit Today ≥ 701,654
Distribution · last window
- Critical2,385
- High8,589
- Medium7,035
- Low793
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-8281——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.71dCVE-2026-60107——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.37dCVE-2026-252607.8 HIG0.0%
——0Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications.63dCVE-2026-28549—0.0%
——0——CVE-2023-23905——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2023-32733——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2026-76830——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.30dCVE-2026-11950——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.84dCVE-2026-51236——
——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.54dCVE-2023-45211——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2026-9012——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33dCVE-2023-41370——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2026-87804——
——0Rejected reason: no security impact14dCVE-2026-17519——
——0Rejected reason: This is rejected.44dCVE-2026-68574——
——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.54dCVE-2023-35058——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2025-24837——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused42dCVE-2023-22445——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused28dCVE-2026-23583——
——0Rejected reason: Withdrawn by requester.22dCVE-2025-36916—0.0%
——0——CVE-2026-22658——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.44dCVE-2026-51234——
——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.54dCVE-2026-198546.1 MED0.0%
——0When the ClickHouse plugin uses Native protocol (the default) with PDC or secure SOCKS, it asks for TLS but the connection library ignores that and talks to ClickHouse in the clear. Username, password, queries, and results can be read on the hop after the proxy. The server certificate is never checked, and a configured client certificate is not sent.23dCVE-2026-82823——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-82814. Reason: This candidate is a reservation duplicate of CVE-2026-82814. Notes: All CVE users should reference CVE-2026-82814 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.23dCVE-2026-73105——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.36dCVE-2023-43613——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2021-47993——
——0Rejected reason: This CVE ID has been rejected.43dCVE-2020-37264——
——0Rejected reason: This CVE ID has been rejected.43dCVE-2026-70613——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2023-28719——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2026-56875——
——0Rejected reason: reserved but not needed33dCVE-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.54dCVE-2025-35988——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused42dCVE-2026-76161——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.18dCVE-2023-39942——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2026-29033——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.44dCVE-2023-38260——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27dCVE-2026-51231——
——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.54dCVE-2026-18862——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.35dCVE-2023-22658——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27d