Vulnerabilities exploitable today
376,337in 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,713
New KEV · 24H0
Exploit Today ≥ 701,646
Distribution · last window
- Critical2,383
- High8,770
- Medium6,812
- Low735
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2023-20950—0.3%
——0——CVE-2025-27033—0.3%
——0——CVE-2026-23217—0.3%
——0——CVE-2023-20825—0.3%
——0——CVE-2023-32871—0.3%
——0——CVE-2025-26463—0.3%
——0——CVE-2026-818228.4 HIG0.3%
——0The vulnerability, if exploited, could allow a miscreant with read access to PIMBoards project files to reverse engineer PIMBoards users’ app-native passwords through computational brute-forcing of weak hashes, potentially allowing elevation to a PIMBoards administrator user.6dCVE-2026-41704—0.3%
——0——CVE-2018-9391—0.3%
——0——CVE-2022-4048—0.3%
——0——CVE-2024-20026—0.3%
——0——CVE-2018-9392—0.3%
——0——CVE-2023-40636—0.3%
——0——CVE-2023-40108—0.3%
——0——CVE-2023-42653—0.3%
——0——CVE-2018-9463—0.3%
——0——CVE-2022-20376—0.3%
——0——CVE-2026-97286.4 MED0.3%
——0The userspace syscall verifier z_vrfy_mbox_send() in drivers/mbox/mbox_handlers.c validated the nested msg->data/msg->size fields by reading them directly out of live userspace memory, and then forwarded the original, still-mutable userspace struct mbox_msg * pointer to z_impl_mbox_send() and the underlying driver. Between the access check and the driver's use of msg->data, the validated pointer could be replaced, leaving a time-of-check/time-of-use window.
On a system built with CONFIG_USERSPACE, any unprivileged userspace thread may invoke the mbox_send() system call. A second thread sharing the caller's address space can race to overwrite msg->data with a supervisor (kernel) address after the verifier's bounds check has passed but before the driver dereferences it. The driver then reads from the attacker-chosen address in supervisor context (for example memcpy(&data32, msg->data, msg->size) in the NXP mailbox driver, whose bytes are subsequently emitted to the peer mailbox endpoint).
The impact is a userspace-to-supervisor access-control bypass: disclosure of kernel memory contents (high confidentiality impact), or, for an invalid/unmapped target address, a faulting kernel read causing denial of service. The fix snapshots the entire struct mbox_msg into a kernel-stack copy with k_usermode_from_copy() and validates and forwards that immutable copy, closing the race.23dCVE-2025-6521—0.3%
——0——CVE-2018-9462—0.3%
——0——CVE-2025-327454.2 MED0.3%
——0Dell PowerFlex Manager, version(s) <=4.6.2, contain(s) an Improper Certificate Validation vulnerability. An unauthenticated attacker with adjacent network access could potentially exploit this vulnerability, leading to Information tampering.56dCVE-2024-20091—0.3%
——0——CVE-2026-43305—0.3%
——0——CVE-2018-9374—0.3%
——0——CVE-2025-21432—0.3%
——0——CVE-2025-48538—0.3%
——0——CVE-2022-39883—0.3%
——0——CVE-2024-20075—0.3%
——0——CVE-2018-9393—0.3%
——0——CVE-2026-286587.8 HIG0.3%
——0In findMetaAuthUid of AccountsDb.java, there is a possible frp bypass due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.2dCVE-2024-29783—0.3%
——0——CVE-2023-21139—0.3%
——0——CVE-2026-487912.0 LOW0.3%
——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.8dCVE-2025-21445—0.3%
——0——CVE-2018-9404—0.3%
——0——CVE-2018-9439—0.3%
——0——CVE-2025-12439—0.3%
——0——CVE-2023-40651—0.3%
——0——CVE-2025-21444—0.3%
——0——CVE-2018-9397—0.3%
——0——