Vulnerabilities exploitable today
374,073in 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,710
New KEV · 24H0
Exploit Today ≥ 701,645
Distribution · last window
- Critical2,342
- High8,460
- Medium6,416
- Low712
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2024-2924—25.4%
——8——CVE-2024-10460—25.4%
——8——CVE-2025-34323—25.4%
——8——CVE-2025-9841—25.4%
——8——CVE-2017-1773—25.4%
——8——CVE-2026-6490—25.4%
——8——CVE-2025-64713—25.4%
——8——CVE-2026-591986.5 MED25.4%
——8Pillow is a Python imaging library. From 5.2.0 until 12.3.0, Pillow's TGA RLE encoder reads past its packed row buffer when saving a mode 1 image with TGA RLE compression, allowing adjacent process heap bytes to be copied into the generated TGA file. This issue is fixed in version 12.3.0.63dCVE-2023-2872—25.4%
——8——CVE-2025-2271—25.4%
——8——CVE-2024-2542—25.4%
——8——CVE-2025-45862—25.4%
——8——CVE-2004-2001—25.4%
——8——CVE-2025-22388—25.4%
——8——CVE-2025-504857.1 HIG25.4%
——8Improper session invalidation in the component /crm/change-password.php of PHPGurukul Online Course Registration v3.1 allows attackers to execute a session hijacking attack.72dCVE-2017-18421—25.4%
——8——CVE-2025-3104—25.4%
——8——CVE-2023-43116—25.4%
——8——CVE-2026-585997.8 HIG25.4%
——8Heap-based buffer overflow in Microsoft Windows Codecs Library allows an unauthorized attacker to execute code locally.6dCVE-2022-30337—25.4%
——8——CVE-2023-2875—25.4%
——8——CVE-2026-4844—25.4%
——8——CVE-2025-0521—25.4%
——8——CVE-2023-42798—25.4%
——8——CVE-2026-878754.3 MED25.4%
——8The cupsUTF32ToUTF8() function in CUPS's cups/transcode.c lacks a source-length bound and can read past the end of the source buffer, resulting in a heap out-of-bounds read. This is reachable via SNMP supply-description parsing in backend/snmp-supplies.c with attacker-controlled content.4dCVE-2025-8812—25.4%
——8——CVE-2025-11788—25.4%
——8——CVE-2022-491598.8 HIG25.4%
——8In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Implement ref count for SRB
The timeout handler and the done function are racing. When
qla2x00_async_iocb_timeout() starts to run it can be preempted by the
normal response path (via the firmware?). qla24xx_async_gpsc_sp_done()
releases the SRB unconditionally. When scheduling back to
qla2x00_async_iocb_timeout() qla24xx_async_abort_cmd() will access an freed
sp->qpair pointer:
qla2xxx [0000:83:00.0]-2871:0: Async-gpsc timeout - hdl=63d portid=234500 50:06:0e:80:08:77:b6:21.
qla2xxx [0000:83:00.0]-2853:0: Async done-gpsc res 0, WWPN 50:06:0e:80:08:77:b6:21
qla2xxx [0000:83:00.0]-2854:0: Async-gpsc OUT WWPN 20:45:00:27:f8:75:33:00 speeds=2c00 speed=0400.
qla2xxx [0000:83:00.0]-28d8:0: qla24xx_handle_gpsc_event 50:06:0e:80:08:77:b6:21 DS 7 LS 6 rc 0 login 1|1 rscn 1|0 lid 5
BUG: unable to handle kernel NULL pointer dereference at 0000000000000004
IP: qla24xx_async_abort_cmd+0x1b/0x1c0 [qla2xxx]
Obvious solution to this is to introduce a reference counter. One reference
is taken for the normal code path (the 'good' case) and one for the timeout
path. As we always race between the normal good case and the timeout/abort
handler we need to serialize it. Also we cannot assume any order between
the handlers. Since this is slow path we can use proper synchronization via
locks.
When we are able to cancel a timer (del_timer returns 1) we know there
can't be any error handling in progress because the timeout handler hasn't
expired yet, thus we can safely decrement the refcounter by one.
If we are not able to cancel the timer, we know an abort handler is
running. We have to make sure we call sp->done() in the abort handlers
before calling kref_put().34dCVE-2026-325915.2 MED25.4%
——8A flaw was found in Red Hat Quay's Proxy Cache configuration feature. When an organization administrator configures an upstream registry for proxy caching, Quay makes a network connection to the specified registry hostname without verifying that it points to a legitimate external service. An attacker with organization administrator privileges could supply a crafted hostname to force the Quay server to make requests to internal network services, cloud infrastructure endpoints, or other resources that should not be accessible from the Quay application.5dCVE-2025-20257—25.4%
——8——CVE-2020-8107—25.4%
——8——CVE-2017-18819—25.4%
——8——CVE-2024-9020—25.4%
——8——CVE-2025-11351—25.4%
——8——CVE-2021-28714—25.4%
——8——CVE-2016-0669—25.4%
——8——CVE-2020-8902—25.4%
——8——CVE-2025-28032—25.4%
——8——CVE-2024-5667—25.4%
——8——CVE-2025-4568—25.3%
——8——