As reported by ChainCatcher on November 17, 2026, citing CryptoSlate, Lightning Network developers fixed an LND vulnerability that could cause a node to misread channel records after a restart. Whether the flaw was exploited or caused any loss of funds had not been confirmed.
The issue involved a 16-bit counter used to record the number of entries when channel updates were saved and restored. 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 hashed timelock contracts (HTLCs), compromising the integrity of its payment-channel accounting.
According to the developers, a connected node could drive up the entry count by repeatedly sending transaction-fee updates and commitment signatures while withholding required revocation messages. LND released v0.21.8-beta and v0.2.8-beta on November 11, adding a safeguard when writing records and validation when loading older records.

