30e0566f-8
BTCPay Server patches five Nginx flaws enabling remote code execution
BTCPay Server released an emergency update for five Nginx vulnerabilities that CERT-EU said could enable remote code execution without login, while no attacks had been reported.

Outputs
BTCPay Server issued an emergency update for five Nginx vulnerabilities.
The update installs Nginx version 1.31.9 for self-hosted Bitcoin payment deployments.
CERT-EU said the flaws could allow remote code execution without login; no attacks were reported as of Wednesday.
Researchers demonstrated how to exploit one of the five vulnerabilities.
The release follows separate August and November incidents involving stolen funds and Lightning Network node credentials.
By Nathan Brooks
BTCPay Server has issued an emergency update for five vulnerabilities in Nginx, the software that routes incoming web traffic to its self-hosted Bitcoin payment application, according to BTCPay and a Wednesday advisory from the European Union’s cybersecurity response team, CERT-EU.
In its advisory, CERT-EU said the flaws could “allow attackers to remotely run malicious code on vulnerable servers without logging in.” Researchers demonstrated how to exploit one vulnerability, but the agency reported no attacks involving any of the five as of Wednesday.
That evidence leaves a narrow but consequential risk picture. A working exploit against one flaw establishes technical feasibility, while no reported attacks establishes only that the agency had not identified exploitation by Wednesday. It does not remove the access path described for vulnerable servers.
What does the emergency update change for operators?
BTCPay said the update installs Nginx version 1.31.9 and urged operators to install it “as soon as possible.” For a self-hosted payment operator, the five disclosures become one concrete deployment target rather than five separate troubleshooting exercises: bring the web-routing layer to version 1.31.9.
The affected layer sits in front of the payment application. Remote code execution at that stage could give an attacker control of infrastructure that receives incoming web traffic, without requiring the operator to surrender valid application credentials. The advisory does not report theft through the five Nginx flaws, and CERT-EU’s finding of no known attacks limits what can be said about actual compromise.
BTCPay said operators can install the fix through:
- the project’s maintenance settings;
- a Docker installation; or
- a node platform once that platform makes the update available.
For operators unable to update immediately, BTCPay pointed to a temporary workaround. That measure addresses the immediate patching gap, but the project still asks operators to complete the version 1.31.9 deployment; a workaround should not become the endpoint for a server exposed to code execution without login.
The emergency release follows two earlier BTCPay Server security incidents involving a separate vulnerability that attackers exploited to steal crypto. In August, attackers exploited a flaw to obtain credentials for Lightning Network nodes and steal funds. In November, BTCPay reported Bitcoin and Litecoin hot-wallet thefts on outdated software, saying attackers had used a different method to exploit the August flaw.
Those earlier events should not be collapsed into the current advisory. The source identifies the five Nginx issues as the present emergency, while the August and November losses involved a separate vulnerability, the August flaw and a different method of exploiting it. For operators, the distinction sets two workstreams: patch the web-routing software now and continue maintaining wallet and node software against the credential-theft pattern documented previously.
The immediate consequence is therefore operational rather than protocol-level. BTCPay did not announce changes to Bitcoin, Litecoin or Lightning Network rules. Operators must manage the remediation across different hosting models: maintenance-setting and Docker users can act directly, while node-platform users must wait for the relevant platform release. That creates uneven exposure timelines even when the same five flaws and one target version apply.
The absence of reported attacks as of Wednesday describes observed activity, not the status of the vulnerable code. The next checkpoint is distribution of Nginx 1.31.9: node-platform operators should install it when available, and every other operator should complete the emergency update without waiting.
via x.com (Original)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,574 articles