CryptoSlate
Older Lightning Terminal software could leave a merchant invoice marked settled after a Bitcoin Lightning payment was canceled and its funds returned to the sender. A merchant relying on that status could release goods or credit without receiving payment. Lightning Labs disclosed the issue on Sept. 21, 2026, without reporting a tally of merchant losses.
Why it matters
The mismatch occurred between the payment outcome on the Lightning network and the invoice state stored by the receiving node. A canceled hashed time-locked contract, or HTLC, returned funds to the sender, while the invoice could still appear paid. The sender's funds were not at risk, and the advisory does not describe a failure of Bitcoin's base chain.
The trigger involved Lightning Terminal's tapd and lnd components. With tapd's invoice interceptor enabled, custom wire records could cause ordinary BTC payments carrying an experimental endorsement record to be treated as asset payments. The strict-forwarding rule then canceled the HTLC set, while affected lnd versions could still mark the invoice as settled. The trigger did not require a merchant to have open asset channels.
Market impact
Lightning Terminal v0.15.0-alpha includes fixes for both defects. The tapd trigger was fixed in taproot-assets v0.5.1 and Terminal v0.14.1-alpha, while lnd v0.19.0-beta fixed the invoice-accounting defect. Earlier Terminal releases, taproot-assets through v0.5.0, and lnd 0.18.4-beta through 0.18.5-beta were affected.
For operators unable to update and without asset channels, Lightning Labs identifies --taproot-assets-mode=disable as a way to avoid the observed tapd trigger. The incident highlights the need for merchants to reconcile invoice status with payment settlement before releasing value.
Frequently asked questions
-
What did the Lightning Terminal bug do?
It could leave a merchant invoice marked settled after the Lightning payment was canceled and the funds returned to the sender.
-
Were Bitcoin sender funds at risk?
No. The issue could create a false paid status for the recipient, while the canceled payment returned funds to the sender.
-
Did the vulnerability affect Bitcoin's base chain?
No. The mismatch occurred between Lightning payment settlement and the invoice state recorded by the receiving node.
-
Which Lightning components were involved?
The trigger involved tapd's invoice interceptor and a separate invoice-state defect in lnd. Both components are bundled in affected Lightning Terminal setups.
-
How can affected operators reduce the risk?
Operators should update to Lightning Terminal v0.15.0-alpha or the relevant fixed component versions. Those unable to update and without asset channels can disable asset mode with --taproot-assets-mode=disable.
WuBlockchain
CoinDesk
TheBlock