Vulnerabilidades exploráveis hoje
410,117na visualização atual
Score único que combina CVSS, presença no KEV e EPSS. Cada CVE com sua própria ficha — timeline da publicação até a exploração ativa.
No catálogo KEV1,769
Novos KEV · 24H0
Exploit Today ≥ 701,700
Distribuição · última janela
- Crítica5,499
- Alta20,885
- Média20,028
- Baixa2,062
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2016-5312—99.0%
——30——CVE-2020-25107—99.0%
——30——CVE-2021-345017.8 ALT99.0%
——30Microsoft Excel Remote Code Execution Vulnerability91dCVE-2011-4075—99.0%
——30——CVE-2016-0710—99.0%
——30——CVE-2010-1157—99.0%
——30——CVE-2024-298479.8 CRÍ99.0%
——30Deserialization of untrusted data in the agent portal of Ivanti EPM before 2022 SU6, or the 2024 September update allows a remote unauthenticated attacker to achieve remote code execution.6dCVE-2019-3964—99.0%
——30——CVE-2025-34030—99.0%
——30——CVE-2022-45933—99.0%
——30——CVE-2021-31618—99.0%
——30——CVE-2011-0522—99.0%
——30——CVE-1999-0046—99.0%
——30——CVE-2002-0061—99.0%
——30——CVE-2021-30641—99.0%
——30——CVE-2011-4453—99.0%
——30——CVE-2005-2733—99.0%
——30——CVE-2020-13382—99.0%
——30——CVE-2020-24435—99.0%
——30——CVE-2022-37436—99.0%
——30——CVE-2024-20440—99.0%
——30——CVE-2019-11447—99.0%
——30——CVE-2023-35924—99.0%
——30——CVE-2022-1178—99.0%
——30——CVE-2002-0150—99.0%
——30——CVE-2010-0557—99.0%
——30——CVE-2010-3585—99.0%
——30——CVE-2017-18017—99.0%
——30——CVE-2022-31470—99.0%
——30——CVE-2021-31213—99.0%
——30——CVE-2007-5348—99.0%
——30——CVE-2023-25652—99.0%
——30——CVE-2019-3963—99.0%
——30——CVE-2023-44449—99.0%
——30——CVE-2018-250327.5 ALT99.0%
——30zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.26dCVE-2024-7314—99.0%
——30——CVE-2021-41649—99.0%
——30——CVE-2014-5468—99.0%
——30——CVE-2013-6129—99.0%
——30——CVE-2020-139434.3 MÉD99.0%
——30If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.32d