Vulnerabilities exploitable today
378,026in 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,716
New KEV · 24H0
Exploit Today ≥ 701,651
Distribution · last window
- Critical2,292
- High8,410
- Medium6,689
- Low753
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2024-2374—31.6%
——9——CVE-2009-0014—31.6%
——9——CVE-2022-29519—31.6%
——9——CVE-2025-31721—31.6%
——9——CVE-2024-3915—31.6%
——9——CVE-2024-44549—31.6%
——9——CVE-2026-200506.8 MED31.6%
——9A vulnerability in the Do Not Decrypt exclusion feature of the SSL decryption feature of Cisco Secure Firewall Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.
This vulnerability is due to improper memory management during the inspection of TLS 1.2 encrypted traffic. An attacker could exploit this vulnerability by sending crafted TLS 1.2 encrypted traffic through an affected device. A successful exploit could allow the attacker to cause a reload of an affected device.
Note: This vulnerability only affects traffic that is encrypted by TLS 1.2. Other versions of TLS are not affected.41dCVE-2025-14206—31.6%
——9——CVE-2025-23906—31.6%
——9——CVE-2023-21891—31.6%
——9——CVE-2025-25760—31.6%
——9——CVE-2017-15116—31.6%
——9——CVE-2023-30472—31.6%
——9——CVE-2014-4039—31.6%
——9——CVE-2023-21861—31.6%
——9——CVE-2023-1692—31.6%
——9——CVE-2025-49198—31.6%
——9——CVE-2024-44556—31.6%
——9——CVE-2024-44552—31.6%
——9——CVE-2026-127207.5 HIG31.6%
——9The Kirki WordPress plugin before 6.0.13 does not restrict which classes may be instantiated when it deserialises data that unauthenticated users can store, leading to PHP Object Injection that is triggered when an administrator later reviews the stored data. With a suitable gadget chain present on the site (via another installed Kirki WordPress plugin before 6.0.13, , or an outdated WordPress version), this could be leveraged to perform a variety of attacks, such as remote code execution.26dCVE-2026-615957.7 HIG31.6%
——9djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, `djust.tenants` isolation was enforced only on the HTTP path. The current tenant was stored in `threading.local()` and set exclusively by the HTTP-only `TenantMiddleware`, so on the live (WebSocket/SSE) path `get_current_tenant()` was always `None` during mount and every event handler — and the tenant-aware `QuerySet` manager failed OPEN (returned the unfiltered queryset, ignoring `STRICT_MODE`), disclosing every tenant's rows to whoever held the socket. `threading.local` was additionally shared across connections on the `sync_to_async` executor thread. This issue is fixed in djust 1.0.7. Tenant storage moved to a `contextvars.ContextVar` (per async task); the resolved tenant is bound around WS/SSE mount and every dispatch; both managers scope the base queryset once and fail CLOSED (`.none()` under the default `STRICT_MODE`); and system check S006 warns when `STRICT_MODE=False`. No known workarounds are available on the live path.5dCVE-2026-845386.5 MED31.6%
——9A denial-of-service issue was addressed with improved input validation. This issue is fixed in macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7. A remote attacker may be able to cause a denial-of-service.6dCVE-2026-3915—31.6%
——9——CVE-2025-10871—31.6%
——9——CVE-2025-30915—31.6%
——9——CVE-2025-31736—31.6%
——9——CVE-2023-4823—31.6%
——9——CVE-2026-935927.5 HIG31.6%
——9vLLM versions before 0.28.0 fail to validate the lower bound of token IDs in the /v1/embeddings and /pooling endpoints, allowing unauthenticated attackers to crash the engine by submitting negative token IDs. A single request with a negative token ID triggers a CUDA device-side assertion that poisons the GPU context, causing all subsequent requests to fail until the process restarts.3dCVE-2024-41796—31.6%
——9——CVE-2025-31768—31.6%
——9——CVE-2025-52935—31.6%
——9——CVE-2026-0616—31.6%
——9——CVE-2023-39398—31.6%
——9——CVE-2024-10854—31.6%
——9——CVE-2022-20169—31.6%
——9——CVE-2013-1772—31.6%
——9——CVE-2022-48302—31.6%
——9——CVE-2026-2706—31.6%
——9——CVE-2018-3672—31.6%
——9——CVE-2025-0325—31.6%
——9——