Vulnerabilities exploitable today
369,332in 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,695
New KEV · 24H0
Exploit Today ≥ 701,636
Distribution · last window
- Critical2,113
- High7,551
- Medium5,585
- Low536
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2022-36774—20.6%
——6——CVE-2024-49822—20.6%
——6——CVE-2021-3636—20.6%
——6——CVE-2025-25188—20.6%
——6——CVE-2026-21686—20.6%
——6——CVE-2026-31867—20.6%
——6——CVE-2025-216477.3 HIG20.6%
——6In the Linux kernel, the following vulnerability has been resolved:
sched: sch_cake: add bounds checks to host bulk flow fairness counts
Even though we fixed a logic error in the commit cited below, syzbot
still managed to trigger an underflow of the per-host bulk flow
counters, leading to an out of bounds memory access.
To avoid any such logic errors causing out of bounds memory accesses,
this commit factors out all accesses to the per-host bulk flow counters
to a series of helpers that perform bounds-checking before any
increments and decrements. This also has the benefit of improving
readability by moving the conditional checks for the flow mode into
these helpers, instead of having them spread out throughout the
code (which was the cause of the original logic error).
As part of this change, the flow quantum calculation is consolidated
into a helper function, which means that the dithering applied to the
ost load scaling is now applied both in the DRR rotation and when a
sparse flow's quantum is first initiated. The only user-visible effect
of this is that the maximum packet size that can be sent while a flow
stays sparse will now vary with +/- one byte in some cases. This should
not make a noticeable difference in practice, and thus it's not worth
complicating the code to preserve the old behaviour.39dCVE-2020-8320—20.6%
——6——CVE-2025-11174—20.6%
——6——CVE-2026-730539.0 CRI20.6%
——6SiYuan versions before v3.7.4 contain a cross-site scripting vulnerability in the unicode2Emoji function that fails to sanitize codepoint branch output. Attackers can craft document icons with hex-encoded markup that executes in the renderer with Node integration enabled, achieving arbitrary code execution on the host system.11dCVE-2024-44913—20.6%
——6——CVE-2024-38491—20.6%
——6——CVE-2024-23276—20.6%
——6——CVE-2024-34434—20.6%
——6——CVE-2026-48946—20.6%
——6——CVE-2025-14539—20.6%
——6——CVE-2026-21687—20.6%
——6——CVE-2024-1629—20.5%
——6——CVE-2025-43424—20.5%
——6——CVE-2026-89954.3 MED20.5%
——6The Poll Maker – Versus Polls, Anonymous Polls, Image Polls plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to and including 6.3.7. This is due to insufficient access controls on the 'ays_poll_get_user_information' AJAX action, which serializes and returns the complete WP_User object — including the user_pass (bcrypt password hash), user_email, user_login, user_registered, roles, and all capabilities — without any nonce verification or capability check beyond is_user_logged_in(). This makes it possible for authenticated attackers, with subscriber-level access and above, to retrieve sensitive account data including their own password hash, which WordPress does not expose through any of its standard interfaces and which can be leveraged for offline password-cracking attacks.47dCVE-2022-20676—20.5%
——6——CVE-2024-477147.6 HIG20.5%
——6In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7996: use hweight16 to get correct tx antenna
The chainmask is u16 so using hweight8 cannot get correct tx_ant.
Without this patch, the tx_ant of band 2 would be -1 and lead to the
following issue:
BUG: KASAN: stack-out-of-bounds in mt7996_mcu_add_sta+0x12e0/0x16e0 [mt7996e]33dCVE-2025-50107—20.5%
——6——CVE-2025-23033—20.5%
——6——CVE-2026-568186.5 MED20.5%
——6Netty is an asynchronous, event-driven network application framework. Prior to 4.1.136.Final and 4.2.16.Final, the RedisArrayAggregator Redis codec clears retained partial aggregate state when the maxNestedArrayDepth limit is exceeded, but it does not clear the same state when the sibling maxElements limit is exceeded. A peer can start a valid RESP array, send a bulk string child, then send a nested array header longer than the configured maxElements. Netty throws a decoder exception in decodeRedisArrayHeader, but the existing partial aggregate remains retained in the handler. If the application leaves the channel alive after the exception, later messages are still consumed into the pre-error aggregate, allowing an unauthenticated peer to keep attacker-controlled aggregate state alive across a security-limit exception and pin retained pooled buffers. This issue is fixed in versions 4.1.136.Final and 4.2.16.Final.30dCVE-2023-23357—20.5%
——6——CVE-2025-14636—20.5%
——6——CVE-2024-35150—20.5%
——6——CVE-2026-7528—20.5%
——6——CVE-2026-25728—20.5%
——6——CVE-2025-29773—20.5%
——6——CVE-2025-58352—20.5%
——6——CVE-2024-9521—20.5%
——6——CVE-2024-41948—20.5%
——6——CVE-2024-8653—20.5%
——6——CVE-2025-20793—20.5%
——6——CVE-2026-732848.8 HIG20.5%
——6RustFS is a distributed object storage system built in Rust. RustFS AddServiceAccount in rustfs/src/admin/handlers/service_account.rs accepts an attacker-controlled target_user after only checking CreateServiceAccountAdminAction, passes it to new_service_account, and prepare_service_account_auth sets is_owner for the resulting root-parent service account. This issue is fixed in version 1.0.0-beta.11.25dCVE-2024-5741—20.5%
——6——CVE-2025-67917—20.5%
——6——CVE-2021-29202—20.5%
——6——