Vulnerabilities exploitable today
350,515in 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,651
New KEV · 24H4
Exploit Today ≥ 701,587
Distribution · last window
- Critical1,541
- High5,045
- Medium4,141
- Low344
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2022-20079—1.5%
——0——CVE-2023-21644—1.5%
——0——CVE-2025-20650—1.5%
——0——CVE-2026-28689—1.4%
——0——CVE-2023-50301—1.4%
——0——CVE-2025-12755—1.4%
——0——CVE-2025-15038—1.4%
——0——CVE-2020-0407—1.4%
——0——CVE-2025-48104—1.4%
——0——CVE-2021-0554—1.4%
——0——CVE-2026-6899—1.4%
——0——CVE-2025-58859—1.4%
——0——CVE-2026-24924—1.4%
——0——CVE-2026-501447.1 HIG1.4%
——0ncnn is a high-performance neural network inference framework optimized for the mobile platform. In commit e54f7b1f88434e1d844ea0551b880a1cfb079ce1 and earlier, ncnn allows an out-of-bounds heap write in ncnn::ParamDict::load_param() when Net::load_param() loads a malicious .param model file because the parsed parameter id is checked only against id >= NCNN_MAX_PARAM_COUNT, allowing a negative id to index before the params[NCNN_MAX_PARAM_COUNT] array. This vulnerability is fixed by commit 5a0288f255daa6c3294f77109f67718e434ec020.4dCVE-2026-41568—1.4%
——0——CVE-2022-20537—1.4%
——0——CVE-2022-20536—1.4%
——0——CVE-2025-60171—1.4%
——0——CVE-2025-60173—1.4%
——0——CVE-2026-11967—1.4%
——0——CVE-2025-48502—1.4%
——0——CVE-2023-7271—1.4%
——0——CVE-2026-46654—1.4%
——0——CVE-2022-21755—1.4%
——0——CVE-2025-60169—1.4%
——0——CVE-2021-0694—1.4%
——0——CVE-2021-0428—1.4%
——0——CVE-2026-27183—1.4%
——0——CVE-2023-53769—1.4%
——0——CVE-2021-25467—1.4%
——0——CVE-2021-39736—1.4%
——0——CVE-2026-106677.8 HIG1.4%
——0Zephyr's dynamic kernel-object tracking (kernel/userspace/userspace.c, formerly kernel/userspace.c) maintains a doubly-linked list (obj_list) of dynamically allocated kernel objects. Iteration over this list in k_object_wordlist_foreach() was performed under lists_lock using the SAFE iterator (which caches the next node), but list removal and freeing of nodes was performed under different, disjoint spinlocks: objfree_lock in k_object_free() and obj_lock in unref_check(). On an SMP system, while one CPU iterated obj_list under lists_lock, another CPU could unlink and k_free() the dyn_obj node that the iterator had cached as its next pointer, causing the iterator to dereference freed kernel memory (use-after-free / dangling list traversal). All of the racing operations are reachable from unprivileged user-mode threads via system calls: k_object_alloc/k_object_alloc_size and k_object_release drive removals through unref_check() (under obj_lock), while k_thread_abort and thread creation drive the iteration through k_thread_perms_all_clear()/k_thread_perms_inherit() (under lists_lock). A deprivileged user thread on a CONFIG_SMP + CONFIG_USERSPACE build can therefore corrupt the kernel's object-tracking structures across the userspace security boundary, yielding kernel memory corruption (potential privilege escalation) or a kernel crash (denial of service). The fix removes objfree_lock and serializes every obj_list modification under lists_lock, including holding it across find+remove in k_object_free() and around unref_check() in k_thread_perms_clear(). Affects CONFIG_SMP+CONFIG_USERSPACE+CONFIG_DYNAMIC_OBJECTS configurations; the defect dates to the 2019 spinlockification (commit 8a3d57b6cc6, first released in v1.14.0) and shipped through v4.4.0.5dCVE-2026-24432—1.4%
——0——CVE-2025-60172—1.4%
——0——CVE-2025-60170—1.4%
——0——CVE-2025-11775—1.4%
——0——CVE-2021-39731—1.4%
——0——CVE-2022-21756—1.4%
——0——CVE-2026-25701—1.4%
——0——CVE-2024-34720—1.4%
——0——