Vulnerabilities exploitable today
401,106in 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,754
New KEV · 24H0
Exploit Today ≥ 701,665
Distribution · last window
- Critical3,467
- High15,791
- Medium14,755
- Low1,456
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2020-11854—99.5%
——30——CVE-2015-2794—99.5%
——30——CVE-2019-1439—99.5%
——30——CVE-2026-2043—99.5%
——30——CVE-2012-1182—99.5%
——30——CVE-2015-3087—99.5%
——30——CVE-2004-2086—99.5%
——30——CVE-2005-0116—99.5%
——30——CVE-2001-0925—99.5%
——30——CVE-2019-12255—99.5%
——30——CVE-2018-5378—99.5%
——30——CVE-2012-0297—99.5%
——30——CVE-2016-2774—99.5%
——30——CVE-2012-0013—99.5%
——30——CVE-2023-30547—99.5%
——30——CVE-2022-07787.5 HIG99.5%
——30The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).7dCVE-2021-37918—99.5%
——30——CVE-2017-11467—99.5%
——30——CVE-2023-34260—99.5%
——30——CVE-2026-222007.5 HIG99.5%
——30Enhancesoft osTicket versions 1.18.x prior to 1.18.3 and 1.17.x prior to 1.17.7 contain an arbitrary file read vulnerability in the ticket PDF export functionality. A remote attacker can submit a ticket containing crafted rich-text HTML that includes PHP filter expressions which are insufficiently sanitized before being processed by the mPDF PDF generator during export. When the attacker exports the ticket to PDF, the generated PDF can embed the contents of attacker-selected files from the server filesystem as bitmap images, allowing disclosure of sensitive local files in the context of the osTicket application user. This issue is exploitable in default configurations where guests may create tickets and access ticket status, or where self-registration is enabled.99dCVE-2022-35711—99.5%
——30——CVE-2011-33894.3 NO 99.5%
——30The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.12dCVE-2020-3239—99.5%
——30——CVE-2005-3352—99.5%
——30——CVE-2007-3401—99.5%
——30——CVE-2009-0542—99.5%
——30——CVE-2015-3183—99.5%
——30——CVE-2008-1914—99.5%
——30——CVE-2020-27858—99.5%
——30——CVE-2008-0621—99.5%
——30——CVE-2025-69657.7 HIG99.5%
——30There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.7dCVE-2011-0065—99.5%
——30——CVE-2022-36982—99.5%
——30——CVE-2023-6063—99.5%
——30——CVE-2006-0992—99.5%
——30——CVE-2023-38992—99.5%
——30——CVE-2011-0762—99.5%
——30——CVE-2012-4958—99.5%
——30——CVE-2020-8813—99.5%
——30——CVE-2007-5067—99.5%
——30——