LND fixes channel-update counter overflow that could affect records after a restart

Lightning Network node operators using LND need to account for a fix to how the software saves and restores payment-channel updates. In a November 17, 2026 report citing CryptoSlate, PANews said LND developers had fixed a flaw that could cause a node to misread those records after a restart.

The flaw involved a 16-bit counter used to record the number of entries. At 65,536 entries, the counter could overflow to zero. On restart, a node could then interpret the records as an empty list and omit settled hash time-locked contracts (HTLCs), undermining the integrity of the payment channel’s accounting.

According to the developers cited in the report, a connected peer could drive the entry count toward that limit by repeatedly sending transaction-fee updates and commitment signatures while withholding the required revocation messages. The report describes a possible failure mode, not a confirmed instance of lost records.

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

Further reading