Vulnerabilities exploitable today
369,346in 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,695
New KEV · 24H0
Exploit Today ≥ 701,636
Distribution · last window
- Critical2,106
- High7,541
- Medium5,585
- Low539
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-3581—20.7%
——6——CVE-2025-1745—20.7%
——6——CVE-2025-66361—20.7%
——6——CVE-2026-764015.9 MED20.7%
——6In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Representational State Transfer (REST) API could configure timestamp extraction with a crafted regular expression and matching event data to block a Kafka Connect worker thread, stopping event delivery for the affected connector. The vulnerability is possible because timestamp extraction evaluates customer-supplied regular expressions without a time limit. For more information see Install Splunk Connect for Kafka (https://help.splunk.com/en/data-management/integrate-data-with-add-ons/splunk-connect-for-kafka/2.2/install/install-splunk-connect-for-kafka) and Data ingestion parameters for Splunk Connect for Kafka (https://help.splunk.com/en/data-management/integrate-data-with-add-ons/splunk-connect-for-kafka/2.2/overview/data-ingestion-parameters-for-splunk-connect-for-kafka) in the Splunk documentation.13dCVE-2024-20080—20.7%
——6——CVE-2026-78307.4 HIG20.7%
——6UltraVNC through 1.8.2.2 uses inadequate cryptography in the MS-Logon II authentication scheme (rfbUltraVNC_MsLogonIIAuth). In rfb/dh.cpp the Diffie-Hellman key exchange is performed with parameters that fit in an unsigned 64-bit integer (DH_MAX_BITS controls the prime size). A 64-bit DH key can be broken by Pollard's rho algorithm in under one second on current hardware. Additionally, the private exponent is generated by the rng() function, which multiplies three libc rand() values seeded from time(NULL). With approximately 31 bits of internal state and a time-based seed, the private exponent is recoverable in under a minute by a passive observer. A network attacker who can observe the MS-Logon II handshake (via sniffing, recording, or man-in-the-middle) can derive the shared DH key and decrypt the encapsulated username and password, resulting in full credential disclosure. This affects legacy MS-Logon II connections; MS-Logon III (X25519 + AES-256-GCM) is unaffected.60dCVE-2025-13576—20.7%
——6——CVE-2025-11272—20.7%
——6——CVE-2026-43875—20.7%
——6——CVE-2026-416767.5 HIG20.7%
——6rust-openssl provides OpenSSL bindings for the Rust programming language. From 0.9.27 to before 0.10.78, Deriver::derive (and PkeyCtxRef::derive) sets len = buf.len() and passes it as the in/out length to EVP_PKEY_derive, relying on OpenSSL to honor it. On OpenSSL 1.1.x, X25519, X448, DH and HKDF-extract ignore the incoming *keylen, unconditionally writing the full shared secret (32/56/prime-size bytes). A caller passing a short slice gets a heap/stack overflow from safe code. OpenSSL 3.x providers do check, so this only impacts older OpenSSL. This vulnerability is fixed in 0.10.78.53dCVE-2023-2800—20.7%
——6——CVE-2024-11457—20.7%
——6——CVE-2025-8743—20.7%
——6——CVE-2023-31762—20.7%
——6——CVE-2023-50941—20.7%
——6——CVE-2023-38667—20.7%
——6——CVE-2021-33183—20.7%
——6——CVE-2025-15260—20.7%
——6——CVE-2026-0689—20.7%
——6——CVE-2022-4552—20.7%
——6——CVE-2026-6919—20.7%
——6——CVE-2026-790874.3 MED20.7%
——6Injection in Chrome Tabs in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to potentially bypass system access restrictions via a crafted HTML page. (Chromium security severity: Medium)6dCVE-2026-184067.2 HIG20.7%
——6The SureForms – Contact Form Builder, AI Forms, Payment Form, Survey & Quiz plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Text Field Entity-Encoded Payload in all versions up to, and including, 2.12.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.2dCVE-2024-53502—20.7%
——6——CVE-2025-64112—20.7%
——6——CVE-2024-52502—20.7%
——6——CVE-2025-59050—20.7%
——6——CVE-2023-31763—20.7%
——6——CVE-2023-33187—20.7%
——6——CVE-2025-63498—20.7%
——6——CVE-2019-4394—20.7%
——6——CVE-2024-11436—20.7%
——6——CVE-2026-31897—20.7%
——6——CVE-2022-404886.5 MED20.7%
——6ProcessWire v3.0.200 was discovered to contain a Cross-Site Request Forgery (CSRF).60dCVE-2025-27686—20.7%
——6——CVE-2024-11687—20.7%
——6——CVE-2026-186316.3 MED20.7%
——6A vulnerability was identified in jeequan jeepay up to 3.2.9. This vulnerability affects the function WebSecurityConfig of the file jeepay-manager/src/main/java/com/jeequan/jeepay/mgr/ctrl/sysuser/SysLogController.java of the component PreAuthorize Handler. The manipulation leads to authorization bypass. The attack may be initiated remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.25dCVE-2026-255218.8 HIG20.7%
——6Locutus brings stdlibs of other programming languages to JavaScript for educational purposes. In versions from 2.0.12 to before 2.0.39, a prototype pollution vulnerability exists in locutus. Despite a previous fix that attempted to mitigate prototype pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using String.prototype. This issue has been patched in version 2.0.39.54dCVE-2020-27802—20.7%
——6——CVE-2026-199946.3 MED20.7%
——6A vulnerability was found in Webkul Bagisto up to 2.4.4. Affected by this issue is some unknown functionality of the file /admin/configuration/cache-management/execute of the component Configuration Management. The manipulation of the argument action results in authorization bypass. The attack may be launched remotely. The exploit has been made public and could be used. The vendor confirms: "The reported issues were already identified through our internal security assessment process prior to this notification and are being handled through our established internal security and development lifecycle. Some of these items have already been addressed, while the remaining items are planned for resolution in upcoming product releases."18d