What changed, and why it matters
This commit is the official release marker for Eclair v0.14.4. The release notes included in the commit describe it as a security-hardening patch release with fixes for multiple issues, some of which can be exploited by malicious nodes. The most clearly described issue is a cross-site request forgery (CSRF) risk on the node's HTTP API: because the API uses HTTP basic authentication and accepts form-encoded parameters, any website visited by the node operator could trick the browser into making authenticated API calls. The release mitigates this by rejecting API requests that carry a browser-style Origin header. Other listed fixes cover seed-file validation, interactive transaction funding, remote closing scripts, channel funding/replacement logic, onion routing packet handling, and transaction publishing. The commit itself only changes version numbers, release notes, CI configuration, and build checksums; the actual code fixes are in the referenced parent commits.
Upgrade Eclair nodes to v0.14.4 promptly, as the vendor explicitly recommends upgrading and notes that some issues can be exploited by malicious nodes. Review any custom web front-ends that previously talked directly to the Eclair API and place a backend proxy in front, because direct browser access is now blocked by Origin-header rejection. Monitor the vendor's release notes and follow-up advisories for detailed per-issue guidance.
Security signals we found
Release notes explicitly label the release as containing 'security hardening fixes' exploitable by malicious nodes
HTTP API now rejects Origin-header requests to mitigate browser-based CSRF against basic-authenticated endpoints
Seed file length validation added (commit a07fff5)
Interactive-tx funding hardened against a malicious bitcoind (commit e43fbf6)
Remote closing script updates validated (commit 380feec)
Onion per-hop lengths exceeding packet size are rejected (commit d3a146a)
Unpublishable splices rejected (commit af99418)
Startup safety guard removed, indicating prior development build was considered unsafe
Evidence from the diff
Commit e1c212c439415f993962890ca3a79b09e82540e2 is the v0.14.4 release commit. It bumps Maven versions from 0.15.0-SNAPSHOT to 0.14.4 across pom.xml files, removes a startup safety guard in Boot.scala that had blocked running the previous development snapshot, adds release checksums, updates CI to package rather than test-compile, and finalizes release notes. The security relevance comes from the release notes, which state the release contains ‘security hardening fixes, most originating from project Loupe’ and list roughly 20 commits. The notes explicitly describe a CSRF-like vulnerability in the HTTP API (basic auth cached by browsers + form-encoded endpoints) and its mitigation (reject requests with an Origin header). Other commits address seed length validation, malicious-bitcoind hardening in interactive-tx funding, remote closing script validation, RBF feerate bounding, splice/HTLC relay logic, onion per-hop length validation, and transaction publication edge cases. No CVE or external advisory is present in the supplied materials.
Changed components
Eclair node HTTP APIEclair wallet seed handlingEclair interactive transaction fundingEclair channel splicing / RBF logicEclair HTLC relay and on-the-fly funding logicEclair onion packet parsingEclair transaction publishingEclair release build / packagingInspect captured patch +90 / −82
### .github/workflows/main.yml
@@ -34,7 +34,7 @@ jobs:
# NB: we exclude external API tests from the CI, because we don't want our build to fail because a dependency is failing.
# This means we won't automatically catch changes in external APIs, but developers should regularly run the test suite locally so in practice it shouldn't be a problem.
- name: Build with Maven
- run: ./mvnw test-compile && ./mvnw scoverage:report -DtagsToExclude=external-api
+ run: ./mvnw package -DskipTests && ./mvnw scoverage:report -DtagsToExclude=external-api -Daether.artifactResolver.postProcessor.trustedChecksums=false
- name: Upload coverage to Codecov
uses: codecov/codecov-action@v3
### .mvn/checksums/checksums-workspace.sha256
@@ -0,0 +1,5 @@
+2f9e2267c63aefafafcd9656c68693a3aeac5951111fe0ba91d0c3b42f3672c5 fr/acinq/eclair/eclair-node_2.13/0.14.4/eclair-node_2.13-0.14.4.pom
+55e0d5957fa49ce80663b9d42896c70530556318ed8ad97586b2c2c79986b06c fr/acinq/eclair/eclair-front_2.13/0.14.4/eclair-front_2.13-0.14.4.pom
+ab3bfb39f4ac4cb57d8830e89fb68033ee791ceb5fecd9745b114792e33d79bf fr/acinq/eclair/eclair-core_2.13/0.14.4/eclair-core_2.13-0.14.4.pom
+cd0d88e0240c84f28883c9b8bdf3adb4373b1b20e7a3c22c6c1a0ced4d82c55e fr/acinq/eclair/eclair-core_2.13/0.14.4/eclair-core_2.13-0.14.4-tests.jar
+dd7ab3677026e7ec794f9cf1c36546236d789d98b703c5a669a5da921c51c735 fr/acinq/eclair/eclair-core_2.13/0.14.4/eclair-core_2.13-0.14.4.jar
### docs/release-notes/eclair-v0.14.4.md
@@ -0,0 +1,79 @@
+# Eclair vnext
+
+This is a patch release that contains security hardening fixes, most originating from project Loupe.
+We highly recommend upgrading, as some of these issues can be exploited by malicious nodes.
+
+### API changes
+
+The API now rejects requests that carry an `Origin` header, which means it cannot be used from a web browser anymore.
+
+Our API relies on HTTP basic authentication, which web browsers attach to cross-site requests once it has been cached:
+any web page the node operator visits could then forge authenticated API calls, and since our endpoints accept
+form-encoded parameters, a plain HTML form is enough (the attacker cannot read the response, but the API call has
+already been made). Browsers set the `Origin` header on those requests, while `curl` and `eclair-cli` never do.
+
+Command-line usage is unaffected. If you were serving a web front-end for the API, you now need to put a back-end of
+your own in front of it.
+
+## Verifying signatures
+
+You will need `gpg` and our release signing key E04E48E72C205463. Note that you can get it:
+
+- from our website: https://acinq.co/pgp/drouinf2.asc
+- from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys
+
+To import our signing key:
+
+```sh
+$ gpg --import drouinf2.asc
+```
+
+To verify the release file checksums and signatures:
+
+```sh
+$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
+$ sha256sum -c SHA256SUMS.stripped
+```
+
+## Building
+
+Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):
+
+- Ubuntu 24.04.1
+- Adoptium OpenJDK 21.0.6
+
+Then use the following command to generate the eclair-node packages:
+
+```sh
+./mvnw clean install -DskipTests
+```
+
+That should generate `eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip` with sha256 checksums that match the one we provide and sign in `SHA256SUMS.asc`
+
+(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.
+
+## Upgrading
+
+This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.
+
+## Changelog
+
+- [bafcf3b](https://github.com/ACINQ/eclair/commit/bafcf3b6fc5299a4aa861f6ae84303a26579af5b) Back to dev (#3379)
+- [27438b7](https://github.com/ACINQ/eclair/commit/27438b75ba8117fe5af31d588030bd874a433138) Reject API access from browsers (#3380)
+- [c3e9f5d](https://github.com/ACINQ/eclair/commit/c3e9f5d633050249a745ce98b63991ed7c266340) Update build to improve release process (#3381)
+- [6162e2a](https://github.com/ACINQ/eclair/commit/6162e2aa8f0c696e5e8c7cd5168f0a08ade4c6d0) Use bitcoin-kmp 0.49 (depends on bitcoin-kmp 0.32.0 and secp256k1-kmp 0.24.0) (#3362)
+- [259ea64](https://github.com/ACINQ/eclair/commit/259ea647580b5bb74d6d63e3a1d5ea81bdaad030) Fix flaky tests caused by port allocation race (#3384)
+- [972dfe9](https://github.com/ACINQ/eclair/commit/972dfe995de0a24e8b496c6cf7144e7db377d51d) Upgrade postgresql client from 42.7.11 to 42.7.12 (#3330)
+- [746fcb1](https://github.com/ACINQ/eclair/commit/746fcb1162018c7248b1d4538b555174da77a431) Bound feerate of remote rbf when we contribute (#3388)
+- [a07fff5](https://github.com/ACINQ/eclair/commit/a07fff56d31291a7bc36cf1bb0faa0f1252c9774) Reject seed files with an invalid length (#3389)
+- [e43fbf6](https://github.com/ACINQ/eclair/commit/e43fbf69255ecf40ea06cc5efd57a51cccdc26f9) Harden interactive-tx funding against a malicious bitcoind (#3390)
+- [380feec](https://github.com/ACINQ/eclair/commit/380feec76b0460c06174e3bdaff5a3a28f25618f) Validate remote closing script updates (#3387)
+- [c89af11](https://github.com/ACINQ/eclair/commit/c89af1154673e7fd9eed3142217377ca1d25d8fb) Remove `spendfromchanneladdress` nonce after one sig (#3392)
+- [248893a](https://github.com/ACINQ/eclair/commit/248893a3a59a78b6114152477d1b6e102f2c6a3d) Use published commitment in PostRestartHtlcCleaner (#3393)
+- [6b61581](https://github.com/ACINQ/eclair/commit/6b61581fc35cb48cdd6fd8d4502053323369e5fb) Only relay on-the-fly payment on funded channel (#3394)
+- [d3a146a](https://github.com/ACINQ/eclair/commit/d3a146a085953389e244623e53f940b5ab897692) Reject onion per-hop lengths exceeding packet (#3395)
+- [af99418](https://github.com/ACINQ/eclair/commit/af994180487cf173a1bb20b0835bda1d6b52b4d5) Reject unpublishable splices (#3396)
+- [c96478a](https://github.com/ACINQ/eclair/commit/c96478a8259648ac1744b47770a719a190a8eb09) Settle relayed on-the-fly upstreams on hash reuse (#3399)
+- [9a1ecc9](https://github.com/ACINQ/eclair/commit/9a1ecc99816f2b11dee25824dd03a50072f30fe1) Force-close again when a splice RBF sibling confirms (#3400)
+- [7686dfa](https://github.com/ACINQ/eclair/commit/7686dfadff7c6868cb3ce441550a22f1152b7dff) Keep unsigned settlements when rejecting commands (#3401)
+- [21f1bc8](https://github.com/ACINQ/eclair/commit/21f1bc8db415a46a8cee690e2d067e746764e828) Retry publishing txs evicted by unconfirmed conflicts (#3397)
### docs/release-notes/eclair-vnext.md
@@ -1,72 +0,0 @@
-# Eclair vnext
-
-<insert here a high-level description of the release>
-
-## Major changes
-
-<insert changes>
-
-### Configuration changes
-
-<insert changes>
-
-### API changes
-
-The API now rejects requests that carry an `Origin` header, which means it cannot be used from a web browser anymore.
-
-Our API relies on HTTP basic authentication, which web browsers attach to cross-site requests once it has been cached:
-any web page the node operator visits could then forge authenticated API calls, and since our endpoints accept
-form-encoded parameters, a plain HTML form is enough (the attacker cannot read the response, but the API call has
-already been made). Browsers set the `Origin` header on those requests, while `curl` and `eclair-cli` never do.
-
-Command-line usage is unaffected. If you were serving a web front-end for the API, you now need to put a back-end of
-your own in front of it.
-
-### Miscellaneous improvements and bug fixes
-
-<insert changes>
-
-## Verifying signatures
-
-You will need `gpg` and our release signing key E04E48E72C205463. Note that you can get it:
-
-- from our website: https://acinq.co/pgp/drouinf2.asc
-- from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys
-
-To import our signing key:
-
-```sh
-$ gpg --import drouinf2.asc
-```
-
-To verify the release file checksums and signatures:
-
-```sh
-$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
-$ sha256sum -c SHA256SUMS.stripped
-```
-
-## Building
-
-Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):
-
-- Ubuntu 24.04.1
-- Adoptium OpenJDK 21.0.6
-
-Then use the following command to generate the eclair-node packages:
-
-```sh
-./mvnw clean install -DskipTests
-```
-
-That should generate `eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip` with sha256 checksums that match the one we provide and sign in `SHA256SUMS.asc`
-
-(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.
-
-## Upgrading
-
-This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.
-
-## Changelog
-
-<fill this section when publishing the release with `git log --reverse --abbrev=7 --pretty=format:'- [%h](https://github.com/ACINQ/eclair/commit/%H) %s' v0.14.3... --format=oneline --reverse`>
### eclair-core/pom.xml
@@ -21,7 +21,7 @@
<parent>
<groupId>fr.acinq.eclair</groupId>
<artifactId>eclair_2.13</artifactId>
- <version>0.15.0-SNAPSHOT</version>
+ <version>0.14.4</version>
</parent>
<artifactId>eclair-core_2.13</artifactId>
### eclair-front/pom.xml
@@ -21,7 +21,7 @@
<parent>
<groupId>fr.acinq.eclair</groupId>
<artifactId>eclair_2.13</artifactId>
- <version>0.15.0-SNAPSHOT</version>
+ <version>0.14.4</version>
</parent>
<artifactId>eclair-front_2.13</artifactId>
### eclair-fuzz/pom.xml
@@ -5,7 +5,7 @@
<parent>
<groupId>fr.acinq.eclair</groupId>
<artifactId>eclair_2.13</artifactId>
- <version>0.15.0-SNAPSHOT</version>
+ <version>0.14.4</version>
</parent>
<artifactId>eclair-fuzz_2.13</artifactId>
### eclair-node/pom.xml
@@ -21,7 +21,7 @@
<parent>
<groupId>fr.acinq.eclair</groupId>
<artifactId>eclair_2.13</artifactId>
- <version>0.15.0-SNAPSHOT</version>
+ <version>0.14.4</version>
</parent>
<artifactId>eclair-node_2.13</artifactId>
### eclair-node/src/main/scala/fr/acinq/eclair/Boot.scala
@@ -33,10 +33,6 @@ import scala.util.{Failure, Success}
*/
object Boot extends App with Logging {
try {
- if (!System.getProperty("eclair.allow-unsafe-startup", "false").toBooleanOption.contains(true)) {
- throw new RuntimeException("This version of eclair is unsafe to use: please wait for the next official release to update your node.")
- }
-
val datadir = new File(System.getProperty("eclair.datadir", System.getProperty("user.home") + "/.eclair"))
val config = NodeParams.loadConfiguration(datadir)
if (config.getString("akka.actor.provider") == "cluster") {
### pom.xml
@@ -20,7 +20,7 @@
<groupId>fr.acinq.eclair</groupId>
<artifactId>eclair_2.13</artifactId>
- <version>0.15.0-SNAPSHOT</version>
+ <version>0.14.4</version>
<packaging>pom</packaging>
<modules>Why this scored 84/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.