LND fixes channel-record overflow that could affect accounting after a restart

As reported on November 17, 2026, Lightning Network developers had fixed a vulnerability in LND, a Bitcoin Lightning Network node implementation. According to CryptoSlate, the issue could cause a node to misread saved channel updates after restarting and omit settled hash time-locked contracts (HTLCs) from its records, compromising payment-channel accounting.

The problem involved a 16-bit counter used to record the number of entries when saving and restoring channel updates. At 65,536 entries, the counter could overflow to zero, causing the node to read the record as an empty list after a restart.

Developers said a connected node could drive the entry count toward that limit by repeatedly sending transaction-fee updates and commitment signatures while withholding the required revocation messages. This describes a potential way to trigger the bug, not a confirmed instance of exploitation.

LND released v0.21.8-beta and v0.20.8-beta on November 11, 2026. The fixes add protection when writing records and validate older records when loading them.

Further reading