Vulnerabilidades exploráveis hoje
413,612na 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,712
- Alta22,677
- Média21,178
- Baixa2,161
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2016-2518—96.8%
——29——CVE-2020-4212—96.8%
——29——CVE-2007-5158—96.8%
——29——CVE-2008-2712—96.8%
——29——CVE-2008-1878—96.8%
——29——CVE-2021-28918—96.8%
——29——CVE-2012-4409—96.8%
——29——CVE-2010-1533—96.8%
——29——CVE-2010-3151—96.8%
——29——CVE-2021-21797—96.8%
——29——CVE-2010-4645—96.8%
——29——CVE-2006-2022—96.8%
——29——CVE-2021-229267.5 ALT96.8%
——29libcurl-using applications can ask for a specific client certificate to be used in a transfer. This is done with the `CURLOPT_SSLCERT` option (`--cert` with the command line tool).When libcurl is built to use the macOS native TLS library Secure Transport, an application can ask for the client certificate by name or with a file name - using the same option. If the name exists as a file, it will be used instead of by name.If the appliction runs with a current working directory that is writable by other users (like `/tmp`), a malicious user can create a file name with the same name as the app wants to use by name, and thereby trick the application to use the file based cert instead of the one referred to by name making libcurl send the wrong client certificate in the TLS connection handshake.29dCVE-2013-1602—96.8%
——29——CVE-2026-2534—96.8%
——29——CVE-2015-0086—96.8%
——29——CVE-2008-1307—96.8%
——29——CVE-2018-7074—96.8%
——29——CVE-2018-5094—96.8%
——29——CVE-2023-0777—96.8%
——29——CVE-2016-7279—96.8%
——29——CVE-2015-6051—96.7%
——29——CVE-2009-2576—96.7%
——29——CVE-2018-0491—96.7%
——29——CVE-2011-1734—96.7%
——29——CVE-2018-8236—96.7%
——29——CVE-2020-1299—96.7%
——29——CVE-2018-8292—96.7%
——29——CVE-2016-3296—96.7%
——29——CVE-2018-5380—96.7%
——29——CVE-2006-3193—96.7%
——29——CVE-2019-3816—96.7%
——29——CVE-2019-13585—96.7%
——29——CVE-2007-4476—96.7%
——29——CVE-2021-30970—96.7%
——29——CVE-2020-5776—96.7%
——29——CVE-2017-12500—96.7%
——29——CVE-2008-2040—96.7%
——29——CVE-2002-1718—96.7%
——29——CVE-2019-0845—96.7%
——29——