CVE-2020-26896 json
Prior to 0.11.0-beta, LND (Lightning Network Daemon) had a vulnerability in its invoice database.
published 2020-10-21 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-19426
- cvss
- 8.2
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
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 invoice, the preimage for an expected payment was instead released. A malicious peer could have deliberately intercepted an HTLC intended for the victim node, probed the preimage through a colluding relayed HTLC, and stolen the intercepted HTLC. The impact is a loss of funds in certain situations, and a weakening of the victim's receiver privacy.
Patch / fix
- lightning_network_daemon_project lightning_network_daemon 0.11.0
Exploit prediction
0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-354 Improper Validation of Integrity Check Value
References
-
lists.linuxfoundation.org
/pipermail/lightning-dev/2020-October/002857.html
mailing-list, patch, third-party-advisory
-
gist.github.com
/ariard/6bdeb995565d1cc292753e1ee4ae402d
third-party-advisory
-
lists.linuxfoundation.org
/pipermail/lightning-dev/2020-October/002855.html
mailing-list, third-party-advisory
Sources
- CVE List CVE-2020-26896
- NVD CVE-2020-26896
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.