Vulnerabilities exploitable today
364,588in 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,675
New KEV · 24H0
Exploit Today ≥ 701,620
Distribution · last window
- Critical2,385
- High10,082
- Medium5,024
- Low463
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-69701——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.4dCVE-2026-68575——
——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.25dCVE-2026-15799——
——0Rejected reason: This is a duplicate.29dCVE-2026-62172——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-61436. Reason: This candidate is a duplicate of CVE-2026-61436. Notes: All CVE users should reference CVE-2026-61436 instead of this candidate.41dCVE-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.25dCVE-2026-487912.0 LOW0.0%
——0sigstore-java is a sigstore java client for interacting with sigstore infrastructure. Version 2.0.0 erroneously removed verification of the integrated (Rekor entry) time) against the Fulcio certificate. Version 2.1.0 re-added this verification with enhancements that adhere to the Sigstore verification spec. The old sigstore-conformance test for this check was built incorrectly. This vulnerability impacts only users verifying bundles with `dev.sigstore:sigstore-java:2.0.0`. Older versions are not affected; it is fixed in `dev.sigstore:sigstore-java:2.1.0` A malicious actor may exploit this if they were able to access a users system and exfiltrate the temporary private key used during signing and then reuse an old fulcio certificate later without requiring direct access to the user's credentials. Users may protect themselves by re-verifying their artifacts using the newest sigstore-java or another current sigstore client. Transparency logs may also be audited for unauthorized signatures for a suspected reused identity.12dCVE-2026-22656——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2026-51239——
——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.25dCVE-2026-28184——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.11dCVE-2026-34862—0.0%
——0——CVE-2026-22653——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2026-58461——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.42dCVE-2026-56873——
——0Rejected reason: reserved but not needed7dCVE-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.50dCVE-2026-56874——
——0Rejected reason: reserved but not needed7dCVE-2026-73112——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.7dCVE-2026-70623——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.18dCVE-2023-54381——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.20dCVE-2026-68944——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-67316. Reason: This candidate is a duplicate of CVE-2026-67316. Notes: All CVE users should reference CVE-2026-67316 instead of this candidate.19dCVE-2026-11427——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.4dCVE-2023-7344——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.4dCVE-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.25dCVE-2026-5723——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.3dCVE-2025-27570——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused13dCVE-2023-7347——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.11dCVE-2025-27245——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused13dCVE-2023-54384——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.20dCVE-2026-14170——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.28dCVE-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.48dCVE-2026-61692——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-61454. Reason: This candidate is a duplicate of CVE-2026-61454. Notes: All CVE users should reference CVE-2026-61454 instead of this candidate.43dCVE-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.41dCVE-2025-27076—0.0%
——0——CVE-2026-35028——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2026-40512——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2023-54382——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.20dCVE-2026-35006——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2023-54380——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.20dCVE-2026-76069——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.4dCVE-2026-76632——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5dCVE-2026-73323——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.4d