Vulnerabilities exploitable today
352,317in 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,653
New KEV · 24H0
Exploit Today ≥ 701,590
Distribution · last window
- Critical2,257
- High7,708
- Medium7,032
- Low663
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-43183—2.9%
——1——CVE-2025-48264—2.9%
——1——CVE-2025-48265—2.9%
——1——CVE-2025-4617—2.9%
——1——CVE-2018-25287—2.9%
——1——CVE-2025-43835—2.9%
——1——CVE-2022-20233—2.9%
——1——CVE-2025-4410—2.9%
——1——CVE-2025-20926—2.9%
——1——CVE-2025-53327—2.9%
——1——CVE-2026-20669—2.9%
——1——CVE-2025-57885—2.9%
——1——CVE-2021-39709—2.9%
——1——CVE-2025-47681—2.9%
——1——CVE-2025-4081—2.9%
——1——CVE-2026-43159—2.9%
——1——CVE-2026-21922—2.9%
——1——CVE-2023-21490—2.9%
——1——CVE-2026-534007.8 HIG2.9%
——1In the Linux kernel, the following vulnerability has been resolved:
i2c: core: fix adapter registration race
Adapters can be looked up based on their id using i2c_get_adapter()
which takes a reference to the embedded struct device.
Make sure that the adapter (including its struct device) has been
initialised before adding it to the IDR to avoid accessing uninitialised
data which could, for example, lead to NULL-pointer dereferences or
use-after-free.
Note that the i2c-dev chardev, which is registered from a bus notifier,
currently uses i2c_get_adapter() so the adapter needs to be added to the
IDR before registration.4dCVE-2025-49449—2.9%
——1——CVE-2021-41218—2.9%
——1——CVE-2025-13657—2.9%
——1——CVE-2024-5912—2.9%
——1——CVE-2025-54732—2.9%
——1——CVE-2026-23554—2.8%
——1——CVE-2026-46128—2.8%
——1——CVE-2026-43434—2.8%
——1——CVE-2026-46127—2.8%
——1——CVE-2026-63280—2.8%
——1Joomla Extension - regularlabs.com - Inconsistent CSRF token checks / privilege checks in Regular Labs conditions manager - Conditions administration did not consistently enforce tokens and component/mapped-item permissions.1dCVE-2025-74067.8 HIG2.8%
——1Nokia MantaRay NM is vulnerable to a sudo privilege escalation vulnerability where a local attacker possessing administrative (local admin) privileges can escalate to full root privileges on the host. Successful exploitation results in root-level access to the filesystem and the ability to execute actions as root. The risk can be temporarily mitigated by restricting the set of commands permitted via sudo for the affected accounts.14dCVE-2026-532135.5 MED2.8%
——1In the Linux kernel, the following vulnerability has been resolved:
drm/vc4: fix krealloc() memory leak
Don't just overwrite the original pointer passed to krealloc()
with its return value without checking latter:
MEM = krealloc(MEM, SZ, GFP);
If krealloc() returns NULL, that erases the pointer
to the still allocated memory, hence leaks this memory.
Instead, use a temporary variable, check it's not NULL
and only then assign it to the original pointer:
TMP = krealloc(MEM, SZ, GFP);
if (!TMP) return;
MEM = TMP;
While on it, use krealloc_array().22dCVE-2026-64791—2.8%
——1Joomla Extension - regularlabs.com - Inconsistent CSRF token checks / privilege checks in Regular Labs Extension Manager - Administrator routes and install/update/uninstall processing did not consistently enforce component-management and installation permissions. An unauthorized backend user or CSRF attack could install, update or remove extensions.1dCVE-2026-63684—2.8%
——1Joomla Extension - regularlabs.com - Inconsistent CSRF token checks / privilege checks in various admin/import/export actions of multiple Regular Labs extension - Administrator actions, editor popups and import/export requests lacked consistent token, item-permission and input-validation checks. Unauthorized backend users or CSRF attacks could expose, create or modify extension configuration and items.1dCVE-2022-34385—2.8%
——1——CVE-2026-46146—2.8%
——1——CVE-2025-62975—2.8%
——1——CVE-2026-63265—2.8%
——1Joomla Extension - regularlabs.com - Inconsistent CSRF token checks / privilege checks in various Regular Labs extension AJAX endpoints - Privileged Regular Labs AJAX endpoints did not consistently require valid CSRF tokens, matching component/item permissions and trusted server-generated form configuration. Authenticated lower-privileged users or CSRF attacks could invoke lookups or mutations outside their authorization.1dCVE-2026-529635.5 MED2.8%
——1In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: Bound MIDI endpoint descriptor scans
snd_usbmidi_get_ms_info() validates the internal MIDIStreaming endpoint
descriptor size before using baAssocJackID[], but the descriptor walker can
still return a class-specific endpoint descriptor whose bLength exceeds the
remaining bytes in the endpoint-extra scan.
That leaves later flexible-array reads bounded by bLength, but not by the
remaining bytes in the endpoint-extra scan.
Stop walking when bLength is zero or
extends past the remaining endpoint-extra scan.10dCVE-2026-43209—2.8%
——1——CVE-2026-532495.5 MED2.8%
——1In the Linux kernel, the following vulnerability has been resolved:
ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options
This patch restricts setting Loose Source and Record Route (LSRR)
and Strict Source and Record Route (SSRR) IP options to users
with CAP_NET_RAW capability.
This prevents unprivileged applications from forcing packets to route
through attacker-controlled nodes to leak TCP ISN and possibly other
protocol information.
While LSRR and SSRR are commonly filtered in many network environments,
they may still be supported and forwarded along some network paths.
RFC 7126 (Recommendations on Filtering of IPv4 Packets Containing
IPv4 Options) recommend to drop these options in 4.3 and 4.4.17d