Vulnerabilities exploitable today
367,284in 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,687
New KEV · 24H0
Exploit Today ≥ 701,629
Distribution · last window
- Critical2,311
- High9,414
- Medium5,381
- Low529
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2022-49189—18.0%
——5——CVE-2022-49219—18.0%
——5——CVE-2025-50060—18.0%
——5——CVE-2022-49397—18.0%
——5——CVE-2025-30316—18.0%
——5——CVE-2025-67929—18.0%
——5——CVE-2025-30362—18.0%
——5——CVE-2026-46343—18.0%
——5Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta2, WazuhCommon.end_receiving_file() in framework/wazuh/core/cluster/common.py allows a cluster-authenticated node to delete files outside WAZUH_PATH. A syn_i_w_m_e request with an unknown task_id reaches the cleanup branch, where an attacker-controlled filename is passed to os.path.join without canonicalization or confinement. Absolute paths and traversal sequences can therefore target files such as ossec.conf, jwt_secret.json, TLS certificates, and ruleset files that are accessible to the Wazuh manager process. Deletion can disable the manager, invalidate API tokens, or disrupt cluster and API connectivity. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.13dCVE-2026-826447.5 HIG18.0%
——5WWBN AVideo (current e01e41ecc and earlier) contains a brute-force rate limiting bypass in enforceRateLimit(), which protects login.json.php and 13 other endpoints. The function stores its attempt counter via a cache layer (ObjectYPT::setCacheGlobal) that silently discards writes for any client identified as a bot by isBot(). Because isBot() treats a missing User-Agent header as a bot by default — and also matches common bot identifiers such as 'curl', 'bot', 'crawler', and 'spider' — the counter never increments for such clients, so the rate limit never fires. An unauthenticated attacker can therefore submit unlimited login attempts (e.g., by omitting the User-Agent header or using curl's default User-Agent), enabling unrestricted password-guessing attacks.2dCVE-2022-49488—18.0%
——5——CVE-2022-49180—18.0%
——5——CVE-2022-49043—18.0%
——5——CVE-2022-49209—18.0%
——5——CVE-2025-60079—18.0%
——5——CVE-2025-67513—18.0%
——5——CVE-2026-112557.5 HIG18.0%
——5Insufficient validation of untrusted input in Storage Access API in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)41dCVE-2022-42335—18.0%
——5——CVE-2023-43518—18.0%
——5——CVE-2023-52993—18.0%
——5——CVE-2022-49460—18.0%
——5——CVE-2025-15112—18.0%
——5——CVE-2026-39421—18.0%
——5——CVE-2022-49490—18.0%
——5——CVE-2022-49558—18.0%
——5——CVE-2025-5033—18.0%
——5——CVE-2022-49467—18.0%
——5——CVE-2023-28064—18.0%
——5——CVE-2025-68699—18.0%
——5——CVE-2025-68596—18.0%
——5——CVE-2026-8084—18.0%
——5——CVE-2025-36104—18.0%
——5——CVE-2020-6968—18.0%
——5——CVE-2022-49396—18.0%
——5——CVE-2025-53677—18.0%
——5——CVE-2012-3483—18.0%
——5——CVE-2024-273977.8 HIG18.0%
——5In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: use timestamp to check for set element timeout
Add a timestamp field at the beginning of the transaction, store it
in the nftables per-netns area.
Update set backend .insert, .deactivate and sync gc path to use the
timestamp, this avoids that an element expires while control plane
transaction is still unfinished.
.lookup and .update, which are used from packet path, still use the
current time to check if the element has expired. And .get path and dump
also since this runs lockless under rcu read size lock. Then, there is
async gc which also needs to check the current time since it runs
asynchronously from a workqueue.28dCVE-2024-266607.0 HIG18.0%
——5In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Implement bounds check for stream encoder creation in DCN301
'stream_enc_regs' array is an array of dcn10_stream_enc_registers
structures. The array is initialized with four elements, corresponding
to the four calls to stream_enc_regs() in the array initializer. This
means that valid indices for this array are 0, 1, 2, and 3.
The error message 'stream_enc_regs' 4 <= 5 below, is indicating that
there is an attempt to access this array with an index of 5, which is
out of bounds. This could lead to undefined behavior
Here, eng_id is used as an index to access the stream_enc_regs array. If
eng_id is 5, this would result in an out-of-bounds access on the
stream_enc_regs array.
Thus fixing Buffer overflow error in dcn301_stream_encoder_create
reported by Smatch:
drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn301/dcn301_resource.c:1011 dcn301_stream_encoder_create() error: buffer overflow 'stream_enc_regs' 4 <= 528dCVE-2026-116327.5 HIG18.0%
——5Use after free in TabStrip in Google Chrome prior to 149.0.7827.103 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)41dCVE-2025-60859—18.0%
——5——CVE-2025-13790—18.0%
——5——