Vulnerabilities exploitable today
356,768in 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,662
New KEV · 24H0
Exploit Today ≥ 701,605
Distribution · last window
- Critical2,533
- High10,540
- Medium6,708
- Low668
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-37503—9.0%
——3——CVE-2025-24647—9.0%
——3——CVE-2026-5378—9.0%
——3——CVE-2026-40436—8.9%
——3——CVE-2022-39117—9.0%
——3——CVE-2025-31779—9.0%
——3——CVE-2023-1633—9.0%
——3——CVE-2019-25545—9.0%
——3——CVE-2025-21930—9.0%
——3——CVE-2025-54083—9.0%
——3——CVE-2026-2655—9.0%
——3——CVE-2025-1777—9.0%
——3——CVE-2026-27382—9.0%
——3——CVE-2026-595127.1 HIG9.0%
——3Unauthenticated Cross Site Scripting (XSS) in Product Enquiry for WooCommerce <= 2.2.34.43 versions.18dCVE-2025-21907—9.0%
——3——CVE-2018-11266—9.0%
——3——CVE-2021-47610—9.0%
——3——CVE-2025-22216—9.0%
——3——CVE-2022-34354—9.0%
——3——CVE-2026-361756.8 MED9.0%
——3An issue in the U-Boot component of GNCC GP5 v7.1.76 allows physically-proximate attackers to bypass authentication and gain root access via interrupting the boot sequence and injecting a crafted string into the kernel boot arguments.18dCVE-2025-36106—9.0%
——3——CVE-2019-256676.2 MED9.0%
——3TaskInfo 8.2.0.280 contains a local buffer overflow vulnerability that allows attackers to crash the application by supplying oversized input to registration fields. Attackers can paste excessively long strings into the New User Name or New Serial Number textboxes in the Help menu's registration dialog to trigger a denial of service condition.16dCVE-2026-12031—9.0%
——3——CVE-2024-377748.0 HIG9.0%
——3A Cross-Site Request Forgery (CSRF) in Sunbird DCIM dcTrack v9.1.2 allows authenticated attackers to escalate their privileges by forcing an Administrator user to perform sensitive requests in some admin screens.36dCVE-2025-63079—9.0%
——3——CVE-2023-534328.8 HIG9.0%
——3In the Linux kernel, the following vulnerability has been resolved:
firewire: net: fix use after free in fwnet_finish_incoming_packet()
The netif_rx() function frees the skb so we can't dereference it to
save the skb->len.6dCVE-2025-40193—9.0%
——3——CVE-2019-25546—9.0%
——3——CVE-2025-30102—9.0%
——3——CVE-2026-12029—9.0%
——3——CVE-2023-53011—9.0%
——3——CVE-2025-68146—9.0%
——3——CVE-2020-0036—9.0%
——3——CVE-2024-23462—8.9%
——3——CVE-2026-330187.0 HIG9.0%
——3libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. Versions 1.8.7 and prior contain a Use-After-Free vulnerability via the load_gif() function in fromgif.c, where a single sixel_frame_t object is reused across all frames of an animated GIF and gif_init_frame() unconditionally frees and reallocates frame->pixels between frames without consulting the object's reference count. Because the public API explicitly provides sixel_frame_ref() to retain a frame and sixel_frame_get_pixels() to access the raw pixel buffer, a callback following this documented usage pattern will hold a dangling pointer after the second frame is decoded, resulting in a heap use-after-free confirmed by ASAN. Any application using sixel_helper_load_image_file() with a multi-frame callback to process user-supplied animated GIFs is affected, with a reliable crash as the minimum impact and potential for code execution. This issue has been fixed in version 1.8.7-r1.16dCVE-2025-220055.5 MED9.0%
——3In the Linux kernel, the following vulnerability has been resolved:
ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().
fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything
when it fails.
Commit 7dd73168e273 ("ipv6: Always allocate pcpu memory in a fib6_nh")
moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()
but forgot to add cleanup for fib6_nh->nh_common.nhc_pcpu_rth_output in
case it fails to allocate fib6_nh->rt6i_pcpu, resulting in memleak.
Let's call fib_nh_common_release() and clear nhc_pcpu_rth_output in the
error path.
Note that we can remove the fib6_nh_release() call in nh_create_ipv6()
later in net-next.git.27dCVE-2022-49758—9.0%
——3——CVE-2023-38409—9.0%
——3——CVE-2024-44292—9.0%
——3——CVE-2025-21874—9.0%
——3——