Vulnerabilities exploitable today
363,765in 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,673
New KEV · 24H0
Exploit Today ≥ 701,611
Distribution · last window
- Critical2,917
- High12,238
- Medium7,449
- Low679
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2023-21314—0.5%
——0——CVE-2025-36908—0.5%
——0——CVE-2022-47460—0.5%
——0——CVE-2022-47478—0.5%
——0——CVE-2022-47477—0.5%
——0——CVE-2026-585515.1 MED0.5%
——0Out-of-bounds read vulnerability in the image codec module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.37dCVE-2023-40085—0.5%
——0——CVE-2023-20847—0.5%
——0——CVE-2023-43543—0.5%
——0——CVE-2023-40124—0.5%
——0——CVE-2024-51515—0.5%
——0——CVE-2026-34867—0.5%
——0——CVE-2022-47459—0.5%
——0——CVE-2022-48371—0.5%
——0——CVE-2024-45556—0.5%
——0——CVE-2025-27046—0.5%
——0——CVE-2025-27061—0.5%
——0——CVE-2023-21320—0.5%
——0——CVE-2022-47338—0.5%
——0——CVE-2026-462724.7 MED0.5%
——0In the Linux kernel, the following vulnerability has been resolved:
coresight: tmc-etr: Fix race condition between sysfs and perf mode
When trying to run perf and sysfs mode simultaneously, the WARN_ON()
in tmc_etr_enable_hw() is triggered sometimes:
WARNING: CPU: 42 PID: 3911571 at drivers/hwtracing/coresight/coresight-tmc-etr.c:1060 tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc]
[..snip..]
Call trace:
tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] (P)
tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] (L)
tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc]
coresight_enable_path+0x1c8/0x218 [coresight]
coresight_enable_sysfs+0xa4/0x228 [coresight]
enable_source_store+0x58/0xa8 [coresight]
dev_attr_store+0x20/0x40
sysfs_kf_write+0x4c/0x68
kernfs_fop_write_iter+0x120/0x1b8
vfs_write+0x2c8/0x388
ksys_write+0x74/0x108
__arm64_sys_write+0x24/0x38
el0_svc_common.constprop.0+0x64/0x148
do_el0_svc+0x24/0x38
el0_svc+0x3c/0x130
el0t_64_sync_handler+0xc8/0xd0
el0t_64_sync+0x1ac/0x1b0
---[ end trace 0000000000000000 ]---
Since the enablement of sysfs mode is separeted into two critical regions,
one for sysfs buffer allocation and another for hardware enablement, it's
possible to race with the perf mode. Fix this by double check whether
the perf mode's been used before enabling the hardware in sysfs mode.
mode:
[sysfs mode] [perf mode]
tmc_etr_get_sysfs_buffer()
spin_lock(&drvdata->spinlock)
[sysfs buffer allocation]
spin_unlock(&drvdata->spinlock)
spin_lock(&drvdata->spinlock)
tmc_etr_enable_hw()
drvdata->etr_buf = etr_perf->etr_buf
spin_unlock(&drvdata->spinlock)
spin_lock(&drvdata->spinlock)
tmc_etr_enable_hw()
WARN_ON(drvdata->etr_buf) // WARN sicne etr_buf initialized at
the perf side
spin_unlock(&drvdata->spinlock)
With this fix, we retain the check for CS_MODE_PERF in get_etr_sysfs_buf.
This ensures we verify whether the perf mode's already running before we
actually allocate the buffer. Then we can save the time of
allocating/freeing the sysfs buffer if race with the perf mode.30dCVE-2025-54634—0.5%
——0——CVE-2024-27237—0.5%
——0——CVE-2026-585525.1 MED0.5%
——0Out-of-bounds read vulnerability in the image codec module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.37dCVE-2025-27055—0.5%
——0——CVE-2023-21355—0.5%
——0——CVE-2023-21317—0.5%
——0——CVE-2026-419805.5 MED0.4%
——0Permission control vulnerability in the file preview module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.29dCVE-2025-224247.8 HIG0.4%
——0In multiple locations, there is a possible way to reveal images across users due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.30dCVE-2024-20033—0.4%
——0——CVE-2024-53009—0.4%
——0——CVE-2025-48644—0.4%
——0——CVE-2026-447226.2 MED0.4%
——0pyzipper is a replacement for Python's zipfile that can read and write AES encrypted zip files. Prior to 0.4.0, a Python operator precedence bug in pyzipper/zipfile_aes.py caused the AE-2 format to never be automatically selected during encryption, causing encrypted entries to be written in AE-1 format and exposing the plaintext CRC32 checksum in the ZIP header and, for unseekable zip archives, in the datadescripter section, allowing an attacker who possesses the archive to brute-force candidate plaintexts for small or low-entropy files by comparing CRC32 values. This issue is fixed in version 0.4.0.35dCVE-2024-20045—0.4%
——0——CVE-2024-29755—0.4%
——0——CVE-2025-64315—0.4%
——0——CVE-2025-26431—0.4%
——0——CVE-2026-493085.5 MED0.4%
——0Permission control vulnerability in the clipboard module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.4dCVE-2023-33037—0.4%
——0——CVE-2024-27232—0.4%
——0——CVE-2024-29747—0.4%
——0——