Vulnerabilities exploitable today
377,882in 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,716
New KEV · 24H0
Exploit Today ≥ 701,651
Distribution · last window
- Critical2,336
- High8,527
- Medium6,725
- Low744
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2023-24418—30.8%
——9——CVE-2023-23822—30.8%
——9——CVE-2023-30477—30.8%
——9——CVE-2023-30876—30.8%
——9——CVE-2022-47608—30.8%
——9——CVE-2023-34187—30.8%
——9——CVE-2023-39987—30.8%
——9——CVE-2023-31232—30.8%
——9——CVE-2023-26541—30.8%
——9——CVE-2023-2490—30.8%
——9——CVE-2023-23785—30.8%
——9——CVE-2022-46863—30.8%
——9——CVE-2023-37993—30.8%
——9——CVE-2023-25491—30.8%
——9——CVE-2026-794835.3 MED30.8%
——9FastGPT Community Edition 4.10.0 through 4.14.0 are vulnerable to a NoSQL injection in the POST /api/core/chat/getHistories endpoint. An unauthenticated attacker can inject malicious NoSQL operators via crafted JSON payloads to bypass authorization checks, resulting in unauthorized access to chat history titles of all users across the platform.18dCVE-2020-9927—30.8%
——9——CVE-2023-23871—30.8%
——9——CVE-2023-24389—30.8%
——9——CVE-2023-25712—30.8%
——9——CVE-2023-29434—30.8%
——9——CVE-2022-3154—30.8%
——9——CVE-2023-28778—30.8%
——9——CVE-2023-25787—30.8%
——9——CVE-2026-71205.3 MED30.8%
——9@fastify/static evaluates the allowedPath callback before normalizing dot segments and duplicate path separators in the pathname used for file resolution. Versions up to and including 10.1.1 are affected. An unauthenticated attacker can bypass allowedPath restrictions by requesting equivalent non-canonical pathnames, causing files that were intended to be denied to be served anyway. The bypass does not allow access outside the configured static root by itself, it defeats path-based filtering only. The issue is patched in @fastify/static 10.1.2.53dCVE-2023-24372—30.8%
——9——CVE-2024-5666—30.8%
——9——CVE-2023-24391—30.8%
——9——CVE-2026-59287.5 HIG30.8%
——9Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash.
A bug in the wide character pushback implementation (_IO_wdefault_pbackfail in libio/wgenops.c) causes ungetwc() to operate on the regular character buffer (fp->_IO_read_ptr) instead of the actual wide-stream read pointer (fp->_wide_data->_IO_read_ptr). The program crash may happen in cases where fp->_IO_read_ptr is not initialized and hence points to NULL. The buffer under-read requires a special situation where the input character encoding is such that there are overlaps between single byte representations and multibyte representations in that encoding, resulting in spurious matches. The spurious match case is not possible in the standard Unicode character sets.67dCVE-2023-41733—30.8%
——9——CVE-2023-28932—30.8%
——9——CVE-2025-13407—30.8%
——9——CVE-2023-25716—30.8%
——9——CVE-2023-25461—30.8%
——9——CVE-2023-23732—30.8%
——9——CVE-2023-31091—30.8%
——9——CVE-2023-26012—30.8%
——9——CVE-2023-32130—30.8%
——9——CVE-2023-25704—30.8%
——9——CVE-2023-27557—30.8%
——9——CVE-2014-0421—30.8%
——9——