Lightning Labs Disclosed Software Vulnerability
A glitch in Lightning Terminal incorrectly marked canceled invoices as paid, potentially allowing merchants to release goods.
Updated on Sept. 25, 2026 in Software

Live Poll
Do you trust software providers to be transparent about the financial risks caused by their bugs?
Lightning Labs revealed a high-severity vulnerability that affected its Lightning Terminal, tapd, and lnd software. The flaw caused canceled invoices to be recorded as paid, though Bitcoin base chain assets remained secure.
Why it matters
This vulnerability created a disconnect between software invoice records and actual payment outcomes, risking merchant losses without fund transfers. While sender funds were not impacted, the bug allowed merchants to potentially release goods without receiving payment.
Affected software includes Lightning Terminal, tapd versions up to v0.5.0, and lnd versions 0.18.4-beta through 0.18.5-beta. Fixes were implemented in tapd v0.5.1 and lnd v0.19.0-beta, with Lightning Terminal v0.15.0-alpha bundling both.
The players
Lightning Labs
Lightning Labs is a developer of software solutions designed for the Bitcoin Lightning Network.
The details
The issue stemmed from an invoice interceptor in tapd treating HTLCs with custom wire records as asset payments, while the lnd software concurrently canceled the payment on the wire. This mismatch led the database to incorrectly flag invoices as settled despite the lack of successful funding.
Timeline
Feb. 12, 2025: The tapd trigger was addressed.
May 22, 2025: The lnd accounting error was resolved.
Sept. 21, 2026: Lightning Labs disclosed the vulnerability.
The Tech Race
This incident highlights the ongoing challenges in securing the Lightning Network's invoice protocol against complex reconciliation errors. It underscores the critical need for robust state management as the industry moves toward more complex asset-based payment systems.
Merchants using affected versions of lnd and tapd must ensure they have updated to the patched releases to prevent invoice settlement errors. While consumer funds were not at risk, business operators should audit past transaction records to verify actual payment receipt.
The takeaway
Reliable reconciliation between payment rails and database logs is essential for digital commerce integrity. Users should prioritize timely software updates to mitigate risks of state-mismatch errors in financial systems.
Further reading
For additional context on secure infrastructure, visit the Software section.
Live Poll
Do you trust software providers to be transparent about the financial risks caused by their bugs?






