CVE Watch360,624 in full archive

Vulnerabilities exploitable today

360,624in 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,665

New KEV · 24H0

Exploit Today ≥ 701,608

Distribution · last window

Critical
2,506
High
11,097
Medium
7,083
Low
640

Filters

Window

Severity

Flags

Vulnerabilities360,281–360,320 · 360,624

CVECVSSEPSSKEVRExploitTitleMod.

CVE-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.15d CVE-2026-51288—

—

——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.15d CVE-2026-61839—

—

——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-61451. Reason: This candidate is a duplicate of CVE-2026-61451. Notes: All CVE users should reference CVE-2026-61451 instead of this candidate.31d CVE-2025-24837—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused3d CVE-2025-24488—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused3d CVE-2026-51301—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5d CVE-2025-66322—

0.0%

——0——CVE-2026-23676—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5d CVE-2022-33724—

0.0%

——0——CVE-2026-22652—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5d CVE-2026-22651—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.5d CVE-2021-47991—

—

——0Rejected reason: This CVE ID has been rejected.4d CVE-2026-467347.3 HIG

0.0%

——0Dell Display and Peripheral Manager (DDPM Mac), versions prior to 2.3, contain an Improper Certificate Validation vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Protection mechanism bypass.36d CVE-2025-66331—

0.0%

——0——CVE-2026-70623—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.8d CVE-2026-51231—

——0Rejected reason: ** DUPLICATE ** This CVE Record has been rejected by the Zephyr Project CNA. CVE-2026-10772 was assigned to a vulnerability already covered by CVE-2026-2411, which was assigned earlier for the same defect: the Bluetooth GATT notify/indicate paths check the permissions of the Characteristic Declaration attribute rather than the Characteristic Value attribute, so the encryption/authentication requirements configured on the value are not enforced. Both identifiers describe the same root cause in subsys/bluetooth/host/gatt.c, fixed by the same commit (c3386f92fe81bd10dc23e6a115e6a80a7d863546). Use CVE-2026-2411 instead.14d CVE-2026-32835—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.10d CVE-2026-69124—

—

——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-67320. Reason: This candidate is a duplicate of CVE-2026-67320. Notes: All CVE users should reference CVE-2026-67320 instead of this candidate.9d CVE-2026-51236—

—

——0Rejected reason: This is a duplicate.19d CVE-2026-50268—

0.0%

——0——CVE-2026-6889—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.16d CVE-2023-54388—

—

——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.10d CVE-2025-15065—

0.0%

——0——CVE-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.31d CVE-2025-66332—

0.0%

——0——CVE-2026-58407—

—

——0Rejected reason: Please submit CVE requests for each vulnerability.33d CVE-2026-68574—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.30d CVE-2023-7354—

—

——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.9d CVE-2026-487912.0 LOW

0.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.2d CVE-2026-72905—

—

——0Rejected reason: Further research determined the issue is not a vulnerability.5d CVE-2026-15424—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.3d CVE-2026-58125—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.37d CVE-2023-7355—

—

——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.9d CVE-2025-66333—

0.0%

——0——