The update addresses five issues disclosed by security researchers under the name NGINX2Root. BTCPay Server outlined separate installation steps for dashboard administrators, Docker operators working over SSH, and users who receive updates through node platforms such as Umbrel and Start9.
Administrators can use the dashboard’s Server Settings and Maintenance sections to start the update. Docker operators can connect to the host over SSH, switch to a root shell, open the `btcpayserver-docker` directory and run `btcpay-update.sh`. The project’s documentation says the script retrieves changes from the operator’s current branch, saves available container logs and recreates the services. Users relying on Umbrel or Start9 need to wait for those platforms to distribute the update.
Nginx released fixes in versions 1.30.7 on its stable branch and 1.31.9 on its mainline branch. The releases contain 10 security fixes each. Two of the five issues in BTCPay Server’s alert affect HTTP/2; the others concern HTTP/3, the resolver and the mail proxy module. In a temporary workaround for operators unable to update immediately, a BTCPay Server contributor advised disabling HTTP/2 in the nginx container and reloading nginx after checking its configuration.
Researcher Brian Pak announced the NGINX2Root disclosure on Nov. 18. The researchers said a separate Linux kernel vulnerability could be combined with an nginx flaw to obtain root access. The nginx updates address vulnerabilities beyond HTTP/2, so disabling the protocol is only a temporary measure.
The alert follows a separate incident involving older BTCPay installations. On Nov. 2, crypto.news reported that the project had urged operators to shut down payment servers after reports of funds being taken from Bitcoin hot wallets. BTCPay Server’s incident report said the reports involved Bitcoin and Litecoin and targeted versions 2.4.1 and earlier; version 2.4.2, released Aug. 7, fixed the vulnerability involved. The project said it had seen no impact on servers already running 2.4.2 or later when the warning was issued.

Comments (0)
No comments yet. Be the first!