Disclosure: LND doesn't wait for enough confirmations when closing channels

The issue pertained to the way lnd handled collaboratively closed channels. Previously, lnd would immediately forget such channels after their first on-chain confirmation, neglecting to wait for additional confirmations to safeguard against potential blockchain reorganizations (reorgs). This oversight meant that if a one-block reorg occurred, an attacker could exploit this by publishing any previously revoked state of the channel. Consequently, lnd would fail to execute penalty transactions, leading to possible financial losses up to the total amount of the channel.

The discovery of this flaw was made during tests involving the option_simple_close feature between eclair and lnd in February 2025. The specific bug resided within the code at this GitHub link. Upon identification, the issue was promptly communicated to Laolu, who is part of the lnd team, leading to a swift resolution. The fix was implemented and merged through this pull request, and subsequently included in the release of lnd version 20.0.

To prevent similar vulnerabilities in the future, it is recommended that all lightning nodes adhere to the BOLT standards, which suggest waiting for at least six confirmations before deeming a transaction fully confirmed. While node operators can opt for more than six confirmations for increased security, it is advised against setting the threshold below this number. Fortunately, there have been no reported cases of users being affected by this vulnerability, indicating that the impact was mitigated effectively through prompt corrective actions.