Mentioned in This Article
1. BTCPay Server update closes five Nginx flaws
BTCPay Server, the self-hosted Bitcoin (BTC) payment software, has released an emergency update that patches five security flaws in Nginx, the web server it relies on. The developers urged operators to install it as soon as possible. CERT-EU, the European Union's cybersecurity response team, said in an advisory on Wednesday, November 18, 2026, that the flaws could let attackers run malicious code remotely without authentication.
The update installs Nginx version 1.31.9, according to the project's developers. The weaknesses are not in BTCPay Server's own payment code. They sit in a separate piece of software that almost every deployment uses to receive traffic from the internet, which is why the project chose to push a fix on an urgent basis instead of waiting for a scheduled release.
No attacks using any of the five flaws had been recorded as of Wednesday, CERT-EU reported. Researchers have, however, already demonstrated how one of the vulnerabilities can be exploited, a development that typically shortens the time operators have to act before attempts begin.
2. What is BTCPay Server?
BTCPay Server is open-source software that lets merchants and other organisations accept Bitcoin payments on infrastructure they run themselves. It generates invoices, monitors the network for incoming payments and records them against orders, without a payment company standing between the buyer and the seller.
That design is the main attraction for its users. A business that runs its own instance does not hand custody of its funds to a processor, does not pay processing fees to one, and cannot have its account frozen or closed by a third party. The software can also connect to the Lightning Network, a layer built on top of Bitcoin for fast, low-cost payments, and it supports wallets that stay online so that funds can be moved automatically.
The other side of that independence is responsibility. A hosted processor employs a security team and patches its systems centrally. With self-hosted software, each operator is the administrator of a server that is reachable from the public internet and is directly connected to wallets holding money. When a vulnerability appears, the fix only protects those who install it.
3. What do the Nginx vulnerabilities allow?
The five flaws could allow an attacker to execute malicious code remotely on a vulnerable server without authenticating, according to CERT-EU's advisory. In practical terms, someone on the internet would not need a password, an account or any prior access to the machine in order to attempt an attack.
Remote code execution is among the most serious categories of software vulnerability. It means an outsider can make the targeted system run instructions of the attacker's choosing. Depending on how the server is configured, that can be a starting point for reading data, changing settings, installing further tools or moving on to other software running on the same machine.
The absence of an authentication requirement compounds the problem. Many vulnerabilities can only be used by someone who already holds valid credentials, which limits the pool of potential attackers. A flaw that works without logging in can be probed by anyone able to send traffic to the server, and such weaknesses are often targeted by automated scanning once the technical details become widely known.
CERT-EU's finding that no attacks had been recorded as of Wednesday provides some reassurance, but it describes a moment in time. The fact that researchers have shown a working method for one of the five flaws indicates the issue is not merely theoretical, and it is the reason BTCPay Server's developers framed the update as urgent.
4. From disclosure to patch: why speed matters
Security fixes follow a recognisable sequence. A flaw is found and reported, the maintainers of the affected software prepare a corrected version, and an advisory is published so that administrators know to upgrade. From that point the details are public, and they are available to attackers as well as defenders.
The interval that follows is the most dangerous period for anyone who has not yet updated. Those looking to exploit a flaw can study the fix to work out what was wrong with the earlier version, and a published demonstration removes much of that effort. This is why a vulnerability with a known exploitation method is treated with more urgency than one that has only been described in general terms.
Projects that bundle third-party components, as BTCPay Server does with Nginx, add one more step to that sequence. The fix first has to be released by the maintainers of the component, and then it has to be packaged and delivered to the project's own users. By shipping an update that installs Nginx 1.31.9 and telling operators to apply it as soon as possible, BTCPay Server's developers have completed their part of that chain. The remaining step lies with each operator.
5. Why a web server bug matters for a payment system
Nginx is one of the most widely used web servers in the world, and in a BTCPay Server deployment it performs a specific job. It is the component that receives incoming connections and directs that traffic to the payment application behind it. Every invoice page a customer opens and every administrator login passes through it first.
That position makes it the outermost layer of the system. Software placed there is, by design, exposed to the open internet, and a weakness in it can be reached before any of the payment application's own protections come into play. A fault in the web server is therefore a fault at the front door, even though the application behind it has not changed.
For most websites, a compromised web server is a serious incident in its own right. For a payment server, the stakes are higher because the same machine may also hold the means to move money. Many BTCPay Server installations run alongside a Lightning node or keep a hot wallet, meaning a wallet whose keys are stored on an internet-connected system so that payments can be processed without manual approval. Code execution on a host of that kind is a direct risk to funds, not only to data.
6. How to update BTCPay Server
Operators can apply the fix through the maintenance section of their BTCPay Server settings or through their Docker installation, the developers said. Docker is the container system that most deployments use to run BTCPay Server and its supporting services, Nginx included, so updating the deployment replaces the vulnerable web server with version 1.31.9.
A different route applies to those running BTCPay Server through a packaged node platform, where the software is installed and managed as an app by the platform's own tooling. Those operators should update once their platform provider releases the fix, since the provider controls the version of each component.
For anyone unable to update straight away, BTCPay Server pointed to a temporary workaround. A workaround of this kind reduces exposure while the vulnerable software remains in place, but it is a stopgap. The project's instruction to install the update as soon as possible applies to every self-hosted instance.
7. Two earlier BTCPay Server incidents
This emergency release follows two earlier security incidents involving BTCPay Server, both of which stemmed from a separate vulnerability that attackers used to steal cryptocurrency. Unlike the Nginx flaws, that weakness has no connection to the web server.
In August, attackers exploited the flaw to obtain credentials for Lightning Network nodes and took funds from them. A Lightning node holds Bitcoin in payment channels and must stay online to route and receive payments, so access to its credentials can translate directly into control over the money it manages.
More recently, BTCPay Server reported thefts from hot wallets on instances that were running outdated software. The project said the attackers had found a different method of exploiting the same August flaw. The detail that the affected servers were out of date is significant: a fix existed, and the losses fell on operators who had not yet installed it.
That history gives context to the tone of the latest warning. In both earlier cases, real funds were lost. This time the project is acting before any attack has been recorded, and it is asking operators to close the gap between a patch being available and a patch being applied, which is where the previous thefts occurred.
8. The patching burden of self-hosted payments
The episode illustrates a structural feature of self-hosted financial software. Its security depends not only on the code written by the project but on every component that code is deployed with, including the operating system, the container tooling, the database and the web server. A flaw in any of them can expose the whole installation.
It also depends on a large number of independent administrators acting promptly. BTCPay Server has no central switch that upgrades every instance. Each merchant, service provider or hobbyist running the software has to notice the warning and carry out the update. Some will do so within hours. Others, particularly those who set up a server once and rarely return to it, may leave it unpatched for a long time.
For operators, the immediate task is narrow: confirm that the instance has been updated and that Nginx is running version 1.31.9, or apply the temporary workaround until that is possible. Those who rely on a node platform need to watch for the provider's release and install it when it arrives. With one of the five flaws already shown to be exploitable and no attacks recorded as of Wednesday, the period before exploitation attempts begin is the time in which the update is most valuable.
