As reported on November 17, 2026, Lightning Network developers had fixed an LND software flaw that could cause a node to misread channel records after a restart. ChainCatcher, citing CryptoSlate, reported that there was no confirmation the flaw had been exploited or had caused any loss of funds.
What could go wrong? LND used a 16-bit counter to record the number of entries when saving and restoring channel updates. At 65,536 entries, the counter could wrap to zero. After a restart, a node could then read the record as an empty list and omit settled hashed timelock contracts (HTLCs), undermining the channel’s accounting integrity.
Developers said a connected node could drive the entry count toward that limit by repeatedly sending fee updates and commitment signatures while withholding the required revocation messages. LND released v0.21.8-beta and v0.2.8-beta on November 11, 2026. The fixes add protection when writing records and checks when loading older records.
The reported risk was to channel accounting after a restart. Whether anyone used the flaw, or whether it caused a loss, remained unconfirmed.