Vulnerabilities exploitable today
369,139in 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,694
New KEV · 24H0
Exploit Today ≥ 701,634
Distribution · last window
- Critical2,182
- High7,846
- Medium5,728
- Low553
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2024-24837—19.6%
——6——CVE-2024-40775—19.6%
——6——CVE-2025-25990—19.6%
——6——CVE-2025-23858—19.6%
——6——CVE-2024-46077—19.6%
——6——CVE-2024-13433—19.6%
——6——CVE-2023-2440—19.6%
——6——CVE-2025-41342—19.6%
——6——CVE-2025-46448—19.6%
——6——CVE-2024-12446—19.6%
——6——CVE-2024-56228—19.6%
——6——CVE-2025-32615—19.6%
——6——CVE-2024-12509—19.6%
——6——CVE-2024-12449—19.6%
——6——CVE-2025-27343—19.6%
——6——CVE-2025-41113—19.6%
——6——CVE-2026-479117.8 HIG19.6%
——6Acrobat Reader versions 24.001.30365, 26.001.21651 and earlier are affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.9dCVE-2026-53017.6 HIG19.6%
——6Stored XSS in log viewer in CoolerControl/coolercontrol-ui <4.0.0 allows unauthenticated attackers to take over the service via malicious JavaScript in poisoned log entries43dCVE-2025-24548—19.6%
——6——CVE-2025-41338—19.6%
——6——CVE-2026-567767.4 HIG19.6%
——6n8n before 1.123.55, 2.25.7, and 2.26.2 contains an authorization bypass in the POST /workflows/{workflowId}/test-runs/new endpoint, which authorizes access using the workflow:read scope instead of workflow:execute. An authenticated user with read-only access to a workflow can trigger a real evaluation test run, causing the workflow to execute via the internal workflow runner and resulting in unintended outbound API calls, data mutations, or other side effects in connected downstream systems. The issue primarily affects instances using the Evaluations feature where RBAC project roles grant workflow:read without workflow:execute.58dCVE-2024-11869—19.6%
——6——CVE-2022-495457.8 HIG19.6%
——6In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: Cancel pending work at closing a MIDI substream
At closing a USB MIDI output substream, there might be still a pending
work, which would eventually access the rawmidi runtime object that is
being released. For fixing the race, make sure to cancel the pending
work at closing.32dCVE-2024-42207—19.6%
——6——CVE-2024-56210—19.6%
——6——CVE-2025-61120—19.6%
——6——CVE-2025-32554—19.6%
——6——CVE-2023-524917.8 HIG19.6%
——6In the Linux kernel, the following vulnerability has been resolved:
media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run
In mtk_jpeg_probe, &jpeg->job_timeout_work is bound with
mtk_jpeg_job_timeout_work.
In mtk_jpeg_dec_device_run, if error happens in
mtk_jpeg_set_dec_dst, it will finally start the worker while
mark the job as finished by invoking v4l2_m2m_job_finish.
There are two methods to trigger the bug. If we remove the
module, it which will call mtk_jpeg_remove to make cleanup.
The possible sequence is as follows, which will cause a
use-after-free bug.
CPU0 CPU1
mtk_jpeg_dec_... |
start worker |
|mtk_jpeg_job_timeout_work
mtk_jpeg_remove |
v4l2_m2m_release |
kfree(m2m_dev); |
|
| v4l2_m2m_get_curr_priv
| m2m_dev->curr_ctx //use
If we close the file descriptor, which will call mtk_jpeg_release,
it will have a similar sequence.
Fix this bug by starting timeout worker only if started jpegdec worker
successfully. Then v4l2_m2m_job_finish will only be called in
either mtk_jpeg_job_timeout_work or mtk_jpeg_dec_device_run.32dCVE-2026-24595—19.6%
——6——CVE-2026-780616.3 MED19.6%
——6A vulnerability was determined in vas3k TaxHacker up to 0.8.2. Impacted is the function buildImapConfig of the file lib/email-sync/imap-client.ts of the component Email Sync. Executing a manipulation of the argument host/port can lead to server-side request forgery. It is possible to launch the attack remotely. The pull request to fix this issue awaits acceptance.12dCVE-2021-28710—19.6%
——6——CVE-2024-40959—19.6%
——6——CVE-2026-24561—19.6%
——6——CVE-2025-46446—19.6%
——6——CVE-2024-12697—19.6%
——6——CVE-2025-58410—19.6%
——6——CVE-2025-24539—19.6%
——6——CVE-2025-41114—19.6%
——6——CVE-2024-8974—19.6%
——6——CVE-2025-41345—19.6%
——6——