Vulnerabilities exploitable today
364,217in 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,674
New KEV · 24H0
Exploit Today ≥ 701,611
Distribution · last window
- Critical2,625
- High10,724
- Medium5,986
- Low568
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2022-47343—0.6%
——0——CVE-2023-21247—0.6%
——0——CVE-2022-47342—0.6%
——0——CVE-2023-20611—0.6%
——0——CVE-2023-21168—0.6%
——0——CVE-2026-21015—0.6%
——0——CVE-2023-20995—0.6%
——0——CVE-2026-538004.7 MED0.6%
——0rsync before 3.5.0 contains a symlink race condition vulnerability in the --remove-source-files feature that allows attackers with symlink creation access to cause arbitrary file deletion. Attackers can atomically substitute a symlink for a source file between transfer completion and the unlink() call, causing rsync to delete the symlink target rather than the intended source file.8dCVE-2026-20993—0.6%
——0——CVE-2023-20934—0.6%
——0——CVE-2023-21155—0.6%
——0——CVE-2026-338025.5 MED0.6%
——0A Missing Authorization vulnerability in the CLI of Juniper Networks Junos OS on EX Series allows a local, authenticated attacker to cause a Denial-of-Service (DoS).
On EX2300, EX4000, EX4100, EX4300-MP (Multigigabit) and EX4400 switches, an authenticated, local attacker with no specific permissions or class can execute a specific, privileged CLI 'request' command which will cause complete traffic impact until the system automatically recovers.
This issue affects Junos OS on EX2300, EX4000, EX4100, EX4300-MP (Multigigabit) and EX4400:
* 23.2R2 versions before 23.2R2-S6,
* 23.4 versions before 23.4R2-S8,
* 24.2 versions before 24.2R2-S4,
* 24.4 versions before 24.4R2-S3,
* 25.2 versions before 25.2R2,
* 25.4 versions before 25.4R1-S1.39dCVE-2026-531255.5 MED0.6%
——0In the Linux kernel, the following vulnerability has been resolved:
md: fix array_state=clear sysfs deadlock
When "clear" is written to array_state, md_attr_store() breaks sysfs
active protection so the array can delete itself from its own sysfs
store method.
However, md_attr_store() currently drops the mddev reference before
calling sysfs_unbreak_active_protection(). Once do_md_stop(..., 0)
has made the mddev eligible for delayed deletion, the temporary
kobject reference taken by sysfs_break_active_protection() can become
the last kobject reference protecting the md kobject.
That allows sysfs_unbreak_active_protection() to drop the last
kobject reference from the current sysfs writer context. kobject
teardown then recurses into kernfs removal while the current sysfs
node is still being unwound, and lockdep reports recursive locking on
kn->active with kernfs_drain() in the call chain.
Reproducer on an existing level:
1. Create an md0 linear array and activate it:
mknod /dev/md0 b 9 0
echo none > /sys/block/md0/md/metadata_version
echo linear > /sys/block/md0/md/level
echo 1 > /sys/block/md0/md/raid_disks
echo "$(cat /sys/class/block/sdb/dev)" > /sys/block/md0/md/new_dev
echo "$(($(cat /sys/class/block/sdb/size) / 2))" > \
/sys/block/md0/md/dev-sdb/size
echo 0 > /sys/block/md0/md/dev-sdb/slot
echo active > /sys/block/md0/md/array_state
2. Wait briefly for the array to settle, then clear it:
sleep 2
echo clear > /sys/block/md0/md/array_state
The warning looks like:
WARNING: possible recursive locking detected
bash/588 is trying to acquire lock:
(kn->active#65) at __kernfs_remove+0x157/0x1d0
but task is already holding lock:
(kn->active#65) at sysfs_unbreak_active_protection+0x1f/0x40
...
Call Trace:
kernfs_drain
__kernfs_remove
kernfs_remove_by_name_ns
sysfs_remove_group
sysfs_remove_groups
__kobject_del
kobject_put
md_attr_store
kernfs_fop_write_iter
vfs_write
ksys_write
Restore active protection before mddev_put() so the extra sysfs
kobject reference is dropped while the mddev is still held alive. The
actual md kobject deletion is then deferred until after the sysfs
write path has fully returned.30dCVE-2026-47330—0.6%
——0——CVE-2023-21198—0.6%
——0——CVE-2023-20972—0.6%
——0——CVE-2023-23588—0.6%
——0——CVE-2026-179843.3 LOW0.6%
——0Inappropriate implementation in Browser in Google Chrome on Android prior to 151.0.7922.72 allowed a local attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)19dCVE-2023-21083—0.6%
——0——CVE-2026-41281—0.6%
——0——CVE-2026-660113.3 LOW0.6%
——0ImageMagick before 7.1.2-27 contains a memory leak vulnerability in the magick command-line interface when invalid options are provided. Attackers can trigger memory exhaustion by repeatedly supplying malformed command-line arguments to consume system resources.18dCVE-2023-20998—0.6%
——0——CVE-2023-21090—0.6%
——0——CVE-2026-148675.5 MED0.6%
——0Credentials of built-in users are insecurely stored in the User directory of PcVue projects, all versions prior to 17.0.0. A local attacker could retrieve users’ credentials.
Active Directory accounts are not affected by this vulnerability.44dCVE-2023-20610—0.6%
——0——CVE-2024-29752—0.6%
——0——CVE-2023-42742—0.6%
——0——CVE-2025-47366—0.6%
——0——CVE-2022-47452—0.6%
——0——CVE-2023-21306—0.6%
——0——CVE-2024-20064—0.6%
——0——CVE-2026-4364—0.6%
——0——CVE-2023-21200—0.6%
——0——CVE-2024-43108—0.6%
——0——CVE-2026-28716—0.6%
——0——CVE-2023-20997—0.6%
——0——CVE-2023-21152—0.6%
——0——CVE-2025-47358—0.6%
——0——CVE-2025-32349—0.6%
——0——CVE-2023-20999—0.6%
——0——