Vulnerabilidades exploráveis hoje
413,655na 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,779
Novos KEV · 24H0
Exploit Today ≥ 701,707
Distribuição · última janela
- Crítica5,607
- Alta22,402
- Média20,867
- Baixa2,124
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2005-1513—95.9%
——29——CVE-2024-6036—95.9%
——29——CVE-2011-3271—95.9%
——29——CVE-2017-8747—95.9%
——29——CVE-2012-3792—95.9%
——29——CVE-2019-144397.5 ALT95.9%
——29A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9.2. This occurs when Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the logback jar in the classpath.35dCVE-2011-2697—95.9%
——29——CVE-2014-5261—95.9%
——29——CVE-2007-3109—95.9%
——29——CVE-2019-7824—95.9%
——29——CVE-2018-12815—95.9%
——29——CVE-2009-3382—95.9%
——29——CVE-2001-0013—95.9%
——29——CVE-2018-4912—95.9%
——29——CVE-2025-148847.2 ALT95.9%
——29A vulnerability was detected in D-Link DIR-605 202WWB03. Affected by this issue is some unknown functionality of the component Firmware Update Service. Performing manipulation results in command injection. The attack can be initiated remotely. The exploit is now public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.42dCVE-2008-5359—95.9%
——29——CVE-2018-5737—95.9%
——29——CVE-2005-2968—95.9%
——29——CVE-2007-4924—95.9%
——29——CVE-2007-4478—95.9%
——29——CVE-2020-8615—95.9%
——29——CVE-2015-3331—95.9%
——29——CVE-2026-275779.9 CRÍ95.9%
——29n8n is an open source workflow automation platform. Prior to versions 2.10.1, 2.9.3, and 1.123.22, additional exploits in the expression evaluation of n8n have been identified and patched following CVE-2025-68613. An authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n. The issues have been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate all known vulnerabilities. If upgrading is not immediately possible, administrators should consider the following temporary mitigations. Limit workflow creation and editing permissions to fully trusted users only, and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.108dCVE-2014-9456—95.9%
——29——CVE-2018-16395—95.9%
——29——CVE-2020-0931—95.9%
——29——CVE-2002-1077—95.9%
——29——CVE-2024-44466—95.9%
——29——CVE-2019-19012—95.9%
——29——CVE-2006-4640—95.9%
——29——CVE-2020-0816—95.9%
——29——CVE-2013-4838—95.9%
——29——CVE-2008-1965—95.9%
——29——CVE-2015-5422—95.9%
——29——CVE-2019-10993—95.9%
——29——CVE-2019-12922—95.9%
——29——CVE-2011-4342—95.9%
——29——CVE-2004-0941—95.9%
——29——CVE-2015-7251—95.9%
——29——CVE-2018-14618—95.9%
——29——