The Ledger
Eclair Releases Second Lightning Security Patch in Five Days
ACINQ released Eclair 0.14.5 on October 20, warning that malicious Lightning nodes could exploit some patched issues. The update follows 0.14.4, which blocked browser-originated requests to Eclair’s API.

“We highly recommend upgrading, as some of these issues can be exploited by malicious nodes.”
ACINQ’s Eclair release notes
ACINQ released Eclair 0.14.5 on October 20, warning Lightning node operators that some issues fixed in the update could be exploited by malicious nodes. The release is the project’s second security-focused patch in five days: version 0.14.4 appeared on October 15. ACINQ credits Nuhiat-Arefin and mptfire with responsible disclosures.
The release notes do not identify the vulnerabilities, describe their mechanics or specify which earlier versions are affected. They also do not say whether any attacks occurred. That leaves operators with a clear upgrade recommendation but limited public detail for assessing exposure in existing installations.
Eclair 0.14.5 leaves the flaws unnamed
ACINQ describes 0.14.5 as a patch release containing security hardening fixes. The warning about malicious nodes establishes the potential source of exploitation, but the notes do not connect the fixes to a particular Lightning message, API endpoint or channel operation. They provide no severity ratings or vulnerability identifiers.
That narrow disclosure gives operators little basis to decide whether a specific deployment faces greater risk than another. ACINQ’s stated recommendation is to upgrade, and the release says operators can do so without closing payment channels: stop Eclair, install the new version and restart. The project says the release is compatible with previous Eclair versions.
The October 15 patch blocked browser access
The earlier 0.14.4 update addressed a different, documented risk in Eclair’s administrative API. Its release notes say the API now rejects requests carrying an Origin header, preventing use from web browsers. ACINQ explained that browsers could attach cached HTTP Basic Authentication credentials to cross-site requests, allowing a website visited by an operator to forge authenticated API calls through a plain HTML form.
Command-line access through tools such as curl and eclair-cli was unaffected because those clients do not send the header. Operators serving a browser-based front end for the API were told to put their own backend in front of it. ACINQ has not said that the vulnerabilities addressed in 0.14.5 stem from, or are connected to, that browser issue.
Operators can verify the release before installing
ACINQ publishes a signing key and signed SHA-256 checksums for release files. Its instructions say operators can import the key, verify the signature on SHA256SUMS.asc, then check the downloaded files against the resulting checksums. Those steps let an operator verify the package against the release’s published signature and hashes before restarting a node with the update.
The project also says Eclair builds are deterministic and provides a build environment of Ubuntu 26.04.1 and Adoptium OpenJDK 21.0.12.1 for reproducing its packages. The notes caution that other operating systems or JDK 21 versions may work, but ACINQ has not tested every combination. For operators, the immediate instructions are simpler: update to 0.14.5, verify the release files and restart without closing channels.
Sources
- Original source · Release notes ACINQ on GitHub · page 1 github.com
Other pages read
- ACINQ on GitHub · page 2 github.com
- ACINQ on GitHub · page 3 github.com
- ACINQ on GitHub · page 4 github.com
Related stories
- Study Finds Lightning Platforms Drive Patch Adoption
- LNbits issues 1.7.1 security patch after wallet vulnerability
- Core Lightning flaw let a peer crash nodes by reusing a funding outpoint
- Lightning Labs ships Pi extension for bitcoin-paid AI inference
- Lightning force-closes cost 2–6 times more in fees, preprint finds