Skip to content
Prices
  • BTC$81,476▲ 0.50%
  • ETH$2,416▲ 0.46%
  • BNB$715.39▼ 0.61%
  • XRP$1.30▲ 0.24%
  • SOL$103.87▲ 0.73%
  • TRX$0.3343▼ 0.03%
  • HYPE$79.02▼ 0.13%
  • DOGE$0.0798▲ 0.14%
  • LINK$12.03▼ 1.83%
  • ADA$0.2221▼ 0.15%
  • AVAX$9.86▼ 0.72%

Eclair 0.14.4 blocks browser attack on Lightning node API

ACINQ's Eclair v0.14.4 rejects API calls that carry a browser Origin header, closing a route for malicious webpages to send commands to Lightning nodes.

· · 3 min read

Share
Close-up of source code on a laptop screen (illustrative photo)
Image: Marc Mueller seven11nash / Wikimedia Commons, CC0
On this page

ACINQ has shipped Eclair v0.14.4, a security patch for its Bitcoin Lightning node software that stops a malicious webpage from quietly sending authenticated commands to a node through the operator's own browser. The release went out on 15 October, and the maintainers "highly recommend upgrading," noting that some of the fixed issues can be exploited by malicious nodes.

What the browser fix does

Eclair exposes an optional HTTP API that can read node state, open and close channels, and send or receive payments. According to the release notes, as summarised by CryptoSlate, the risk looked like this:

  • The operator has the API enabled, reachable from their browser, and has already logged in with HTTP Basic authentication, so the browser caches the password.
  • A hostile webpage submits a plain HTML form to the node's API address. The browser attaches the saved credentials automatically.
  • The attacker cannot read the reply, but the command itself still reaches the node — a classic cross-site request forgery pattern.

The patch makes Eclair answer HTTP 403 to any API request that carries an Origin header, whatever its value, before the request is processed. The change was merged on 15 September in pull request #3380.

Who is affected

  • Command-line users: eclair-cli and curl don't send an Origin header, so normal scripted access keeps working.
  • Browser dashboards: any web interface that talks to the API directly — even one hosted on the same origin — now needs a small backend sitting between the browser and Eclair.
  • Everyone: the maintainers stress that the Origin check is not authentication. Keep the API password strong and the API bound to the local machine (loopback), not exposed to the network.

The release also bundles other hardening fixes, most credited to contributor erickcestari and the Loupe project. ACINQ says it is fully compatible with earlier versions: stop the node, upgrade and restart, with no need to close channels. We have not seen reports of the browser issue being exploited.

Why it matters

Lightning nodes are hot wallets: the keys that control channel funds sit on an always-online machine, so the attack surface around them matters more than for cold storage. New to the technology? Our explainer what is the Lightning Network covers channels, routing and the risks. Rogue software touching wallets is a theme this week, after an OpenAI test model spent testnet ETH from a wallet it did not own.

Frequently asked questions

Do I need to upgrade my Eclair node?

ACINQ highly recommends upgrading to v0.14.4 because some of the fixed issues can be exploited by malicious nodes. The release is compatible with earlier versions: stop Eclair, upgrade and restart without closing channels.

Does this affect Phoenix or other Lightning wallets?

The browser fix concerns the HTTP API of self-hosted Eclair nodes. The release notes describe node software, not consumer wallet apps, so check your own wallet provider's announcements.

Will my scripts using eclair-cli or curl break?

No. According to the maintainers, eclair-cli and curl don't send an Origin header, so ordinary API calls are unaffected. Web dashboards that call the API straight from a browser need a backend in between.

Is rejecting the Origin header enough to secure the API?

No. A non-browser client can simply omit the header. The maintainers say authentication and binding the API to the local machine remain essential.

This article is for information only and is not financial advice. Crypto assets are volatile; do your own research. Read our disclaimer

Share

More from Security

View all →

Read next