
BTCPay Server has announced an emergency update for five nginx vulnerabilities on Nov. 18, urging operators of its Bitcoin payment software to install the fix as soon as possible.
Summary
- The update addresses five nginx flaws, including one that can let an attacker run code without signing in when HTTP/2 is enabled.
- Nginx released fixes in version 1.30.7 on its stable branch and 1.31.9 on its mainline branch.
- BTCPay Server pointed Docker operators who cannot update immediately to a temporary workaround that turns off HTTP/2.
- Users running BTCPay Server through Umbrel or Start9 were told to install the update when their platform makes it available.
BTCPay Server said in a pinned post on X that the update covers five flaws disclosed by security researchers under the NGINX2Root name. The project shared separate instructions for administrators who manage their servers through the web dashboard, operators who update Docker installations over SSH, and users who get their updates through a node platform.
How BTCPay Server operators can install the update
Administrators with access to the BTCPay Server dashboard can open Server Settings, select Maintenance, and click Update, according to the project’s server FAQ. Operators managing a Docker installation from the command line can sign in to the host over SSH, switch to a root shell, open the btcpayserver-docker directory, and run the project’s btcpay-update.sh script.
The project’s Docker documentation says the script pulls the latest changes from the branch the operator has checked out, saves the available container logs, and recreates the services.
On the standard Docker deployment, nginx sits in front of BTCPay Server and directs incoming web requests to the payment application or other services configured on the same installation. The networking guide identifies nginx as the component that handles incoming connections on the standard web and HTTPS ports.
BTCPay Server asked users who depend on a node platform for updates to follow that platform’s release schedule, naming Umbrel and Start9 in its instructions. The project gave operators an urgency recommendation, while the installation timing for those users depends on when their platform distributes the update.
The updater saves the container logs it can still access before it replaces the running services, according to the Docker guide. It keeps the five most recent successful log captures. The guide says a saved archive records what was available at the time of capture, so operators checking whether an update completed need to look at the current state of the services as well.
The nginx fixes cover flaws in HTTP/2 and other features
Security researcher Brian Pak announced the NGINX2Root disclosure on Nov. 18. The researchers identified CVE-2026-123007 as a flaw affecting installations with HTTP/2 enabled. On an affected server, the flaw can let a remote attacker execute code without authenticating.
The researchers said a separate Linux kernel vulnerability could be combined with an nginx flaw to gain root access, the highest level of privilege on the host.
The nginx release notice lists fixes for all five issues in both open-source releases. Two of the vulnerabilities affect HTTP/2, and the remaining three concern HTTP/3, the resolver, and the mail proxy module. The stable and mainline releases each contain 10 security fixes in total, including the five identified in BTCPay Server’s announcement. The 1.30.7 and 1.31.9 version numbers refer to nginx, the web server bundled with the standard deployment.
In a follow-up post, BTCPay Server directed operators who could not install the update immediately to guidance from core contributor @ndeet. The workaround disables HTTP/2 inside the nginx container and reloads nginx after checking the configuration. The contributor described the change as temporary, and the nginx release notes list fixes in other components beyond HTTP/2.
An earlier wallet-drain alert involved older BTCPay releases
On Nov. 2, crypto.news reported that BTCPay Server had urged operators to shut down payment servers after receiving reports of funds being taken from Bitcoin hot wallets on older installations.
In its incident report, the project said it received reports involving Bitcoin and Litecoin and identified BTCPay Server 2.4.1 and earlier as the versions targeted. It dated the fix for the vulnerability involved in that incident to Aug. 7, when version 2.4.2 was released.
The project said it received the first theft report by email on Nov. 1 and contacted hosting providers, including LunaNode, to ask them to take affected instances offline as a precaution. Its incident report said several security updates had followed the August fix by the time the theft reports came in.
The project said it had seen no impact from the reported attacks on servers already running 2.4.2 or later when the warning went out.
The project advised operators who still had those older installations when the Nov. 1 warning went out to move to a fresh server with a new wallet. It said the advice applied even if an operator saw no theft or updated the existing server after the warning.
The incident report asked affected operators to preserve relevant logs and transaction records before replacing the old server.
