Vulnerabilidades

Resumen — últimos 7 días

Vulnerabilidades nuevas2635▼ 212 respecto a la semana anterior
Críticas / altas1376▲ 147 respecto a la semana anterior
Nueva explotación activa (KEV)7▼ 3 respecto a la semana anterior
Sin puntuar (sin CVSS)81▼ 449 respecto a la semana anterior
–

5 resultados, ordenados por fecha de publicación (más recientes primero)

CVEEstadoSeveridadEPSS Explotación activaTecnologías afectadasPublicada ▼Modificada Descripción
AplazadaMedia (6.5)0.57%—Lightning Network Daemon LNDAI20/6/202417/6/2026
The Lightning Network Daemon (lnd) - is a complete implementation of a Lightning Network node. A parsing vulnerability in lnd's onion processing logic and lead to a DoS vector due to excessive memory allocation. The issue was patched in lnd v0.17.0. Users should update to a version > v0.17.0 to be protected. Users…
ModificadaMedia (6.5)1.1%—Btcd Project BtcdLightning Network Daemon Project Lightning Network Daemon17/11/202217/6/2026
Lightning Network Daemon (lnd) is an implementation of a lightning bitcoin overlay network node. All lnd nodes before version `v0.15.4` are vulnerable to a block parsing bug that can cause a node to enter a degraded state once encountered. In this degraded state, nodes can continue to make payments and forward HTLCs,…
ModificadaAlta (8.6)1.9%—Lightning Network Daemon Project Lightning Network Daemon4/10/202117/6/2026
Lightning Labs lnd before 0.13.3-beta allows loss of funds because of dust HTLC exposure.
ModificadaAlta (8.2)0.74%—Lightning Network Daemon Project Lightning Network Daemon21/10/202017/6/2026
Prior to 0.11.0-beta, LND (Lightning Network Daemon) had a vulnerability in its invoice database. While claiming on-chain a received HTLC output, it didn't verify that the corresponding outgoing off-chain HTLC was already settled before releasing the preimage. In the case of a hash-and-amount collision with an…
ModificadaMedia (5.3)0.71%—Lightning Network Daemon Project Lightning Network Daemon21/10/202017/6/2026
Prior to 0.10.0-beta, LND (Lightning Network Daemon) would have accepted a counterparty high-S signature and broadcast tx-relay invalid local commitment/HTLC transactions. This can be exploited by any peer with an open channel regardless of the victim situation (e.g., routing node, payment-receiver, or…