Lightning Network LND patches critical vulnerability; node restarts could omit settled payments

First, the most important point: LND, the most widely used node software for Bitcoin’s Lightning Network, has just fixed a deeply buried vulnerability. If an unpatched node restarts, its ledger may “miss” a payment that has already been settled.

Here’s how the vulnerability arose: channel update records are tracked with a 16-bit counter. Once it reaches 65,536, it resets to zero, even though the records themselves remain safely stored on disk. After a restart, the node reads the counter and assumes the list is empty. As a result, the reconstructed channel state may be missing a settled payment contract. More troublingly, a peer node could repeatedly send fee updates and signatures without sending revocation messages, forcing the list to overflow.

As for the fix and the current situation: versions v0.21.8-beta and v0.20.8-beta, released on November 11, have fixed the issue. Excessively long update lists are now rejected, and complete records saved by older versions can also be restored after validation. The development team also says there are currently no confirmed cases of exploitation and no reports of funds being lost as a result.

We believe what’s at risk isn’t the coins, but the “accounting”—the Lightning Network’s biggest fear is when the two sides of a channel can’t reconcile their records. If you run a node, upgrade to the latest version as soon as possible. Don’t wait until the next restart to discover a payment is missing. $BTC