Vulnerabilities exploitable today
356,659in 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,550
- High10,749
- Medium6,931
- Low696
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-63990—7.8%
——2In the Linux kernel, the following vulnerability has been resolved:
bonding: refuse to enslave CAN devices
syzbot reported a kernel paging request crash in
can_rx_unregister() inside net/can/af_can.c. The crash occurs
because a virtual CAN device (vxcan) is being enslaved to a
bonding master.
During the enslavement process, the bonding driver mutates
and modifies the network device states to fit an Ethernet-like
aggregation model. However, CAN devices operate on a completely
different Layer 2 architecture, relying on the CAN mid-layer
private data structure (can_ml_priv) instead of standard
Ethernet structures. Since bonding does not initialize or
maintain these CAN structures, subsequent operations on the
half-enslaved interface (such as closing associated sockets
via isotp_release) lead to a null-pointer dereference when
accessing the CAN receiver lists.
Bonding CAN interfaces is architecturally invalid as CAN lacks
MAC addresses, ARP capabilities, and standard Ethernet
link-layer mechanisms. While generic loopback devices are
blocked globally in net/core/dev.c, virtual CAN devices
bypass this check because they do not carry the IFF_LOOPBACK
flag, despite acting as local software-loopbacks.
Fix this by explicitly blocking network devices of type
ARPHRD_CAN from being enslaved at the very beginning of
bond_enslave(). This prevents illegal state mutations,
eliminates the resulting KASAN crashes, and avoids potential
memory leaks from incomplete socket cleanups.
As the CAN support has been added a long time after bonding
the Fixes-tag points to the introduction of ARPHRD_CAN that
would have needed a specific handling in bonding_main.c.9dCVE-2024-46793—7.8%
——2——CVE-2026-26225—7.8%
——2——CVE-2025-53914—7.8%
——2——CVE-2025-21649—7.8%
——2——CVE-2026-493846.1 MED7.8%
——2In JetBrains PyCharm before 2025.3.4 stored XSS in Jupyter notebook Markdown cells was possible17dCVE-2025-12823—7.8%
——2——CVE-2021-27785—7.8%
——2——CVE-2025-33217—7.8%
——2——CVE-2024-26740—7.8%
——2——CVE-2019-1809—7.8%
——2——CVE-2025-4661—7.8%
——2——CVE-2025-2515—7.8%
——2——CVE-2026-33311—7.8%
——2——CVE-2025-12376—7.8%
——2——CVE-2026-23405—7.8%
——2——CVE-2025-54222—7.8%
——2——CVE-2025-8045—7.8%
——2——CVE-2025-20076—7.8%
——2——CVE-2024-13976—7.8%
——2——CVE-2026-32112—7.8%
——2——CVE-2026-25576—7.8%
——2——CVE-2025-71244—7.8%
——2——CVE-2026-221885.5 MED7.8%
——2The deploy-stub component in Panda3D versions up to and including 1.10.16 contains a denial of service vulnerability due to unbounded stack allocation. The deploy-stub executable allocates argv_copy and argv_copy2 using alloca() based directly on the attacker-controlled argc value without validation. Supplying a large number of command-line arguments can exhaust stack space and propagate uninitialized stack memory into Python interpreter initialization, resulting in a reliable crash and undefined behavior.25dCVE-2024-38335—7.8%
——2——CVE-2025-37824—7.8%
——2——CVE-2024-24864—7.8%
——2——CVE-2025-13939—7.8%
——2——CVE-2026-55188—7.8%
——2——CVE-2025-40152—7.8%
——2——CVE-2026-140464.3 MED7.8%
——2Inappropriate implementation in CustomTabs in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Low)38dCVE-2022-49921—7.8%
——2——CVE-2026-64482—7.8%
——2In the Linux kernel, the following vulnerability has been resolved:
ALSA: gus: check snd_ctl_new1() return value
snd_ctl_new1() can return NULL when memory allocation fails.
snd_gf1_pcm_volume_control() does not check the return value before
dereferencing kctl->id.index, which can lead to a NULL pointer
dereference.
Add a NULL check after snd_ctl_new1() and return -ENOMEM if it fails.14dCVE-2025-21978—7.8%
——2——CVE-2021-47569—7.8%
——2——CVE-2026-389727.8 HIG7.8%
——2Notepad3 through 6.25.822.1 contains a DLL search-order hijacking vulnerability in the About-dialog code path in src/Notepad3.c. The application calls LoadLibrary(L"MSFTEDIT.DLL") with a bare DLL name, which allows a local attacker to place a malicious MSFTEDIT.DLL in the application directory or another preferred DLL search location and achieve arbitrary code execution in the context of the user when the About dialog is opened.31dCVE-2024-1446—7.8%
——2——CVE-2026-4587—7.8%
——2——CVE-2025-5275—7.8%
——2——CVE-2025-64781—7.8%
——2——