A server rack with the BTCPay Server logo and several cracks in its door, being repaired by a robotic arm that bolts an orange patch over the damage.

BTCPay Server Issues Emergency Update for Five nginx Flaws

BTCPay Server announced an emergency update on Nov. 18 for five nginx vulnerabilities disclosed as NGINX2Root, including CVE-2026-123007, which allows unauthenticated remote code execution on HTTP/2-enabled installs. Docker operators should verify nginx 1.31.9.

Alejandro Silva RamírezNovember 18, 20262 min read
Share

Five vulnerabilities in nginx, the web server that sits in front of many self-hosted installations of BTCPay Server, have prompted the project to announce an emergency update on Nov. 18. It urged operators of its Bitcoin payment software to install the fix as soon as possible.

The most serious of the five, tracked as CVE-2026-123007, affects installations with HTTP/2 enabled and can let a remote attacker execute code without authenticating. Security researcher Brian Pak announced the disclosure, which goes by the name NGINX2Root, on the same day. The researchers also said a separate Linux kernel vulnerability could be chained with an nginx flaw to gain root access, which would turn a web-server bug into full control of the host machine.

BTCPay Server said in a pinned X post that the update covers the five flaws disclosed under that name. Two affect HTTP/2, while the other three concern HTTP/3, the resolver and the mail proxy module. Nginx has shipped fixes in version 1.30.7 on its stable branch and 1.31.9 on its mainline branch, and each release contains 10 security fixes in total.

One detail matters for operators who look for a BTCPay version bump: the fix updates the web-server dependency rather than BTCPay's own version number. Docker operators should therefore verify that their nginx container is running 1.31.9.

How to update

Dashboard administrators can go to Server Settings, then Maintenance, then Update. Docker operators can run btcpay-update.sh over SSH from the btcpayserver-docker directory, per the project documentation. Umbrel and Start9 users were told to install the update once their platform makes it available, which leaves the timing outside their control.

Docker operators who cannot update immediately were pointed to a temporary workaround from core contributor @ndeet that disables HTTP/2 in the nginx container and reloads nginx. It is a stopgap, not a cure. The nginx release notes list fixes in components beyond HTTP/2, so a server running the workaround remains exposed to the other flaws.

Context

Self-hosted payment software puts the operator in the role of system administrator, and that role extends to the layers beneath the application. A flaw in a dependency like nginx reaches every deployment that exposes it, however carefully the payment code itself was written. That is the structural lesson of this update.

It also lands in a difficult month for the project. On Nov. 2, BTCPay told operators to shut down servers after funds were taken from hot wallets on version 2.4.1 and earlier. That issue is separate from the nginx update, and its fix had shipped in 2.4.2 on Aug. 7. The two events share no cause, but both reward operators who patch quickly.

Discussion

Loading comments...