Eclair v0.14.4 Blocks Browser-Proxy Node API Commands

Eclair, the Lightning Network node software, has blocked a path that allowed browsers to send API commands using stored authentication credentials. The new version refuses browser requests but emphasizes that API authentication and network access restrictions remain necessary.
ACINQ, the developer, released Eclair v0.14.4 on October 15. The update sends an HTTP 403 response before processing any request with an Origin header, regardless of its value. Eclair's official API documentation states that browsers set this header and blocking such requests prevents cross-site request forgery (CSRF).
The release notes indicate v0.14.4 remains compatible with previous versions. The issue stemmed from browsers reusing stored HTTP Basic authentication for requests initiated from other sites. If a user visited a malicious page, it could send requests to the Eclair API and relay node commands without reading responses.
Eclair's API supports not only node status checks but also Lightning channel opening/closing and payment sending/receiving. Thus, an environment where the API is enabled, the operator's browser can access the API, and authentication credentials are saved becomes vulnerable.
No confirmed damage or actual exploitation cases have been reported. This measure affects web interfaces that directly call APIs from browsers—even if they come from the same source, browsers cannot make direct API calls, requiring operators to add a separate backend between browser and Eclair.
However, standard curl or eclair-cli requests without an Origin header can still use the API as before. Blocking Origin headers acts as a filter for browser-issued requests; non-browser clients omit this header, so absence of the header alone does not guarantee trustworthiness.
ACINQ clarified in its update notes that this measure does not replace authentication. Its documentation advises against exposing APIs externally, noting they are disabled by default and bound to localhost (127.0.0.1) by default. Operators should maintain these settings along with authentication.
The v0.14.4 update can be applied without closing channels—simply stop Eclair, upgrade the version, and restart. This change blocks a path where browsers reuse authentication to send commands but does not eliminate external API exposure risks entirely.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: Eclair v0.14.4, 브라우저 경유 노드 API 명령 차단