78623327-9
BTCPay Server patches five nginx flaws after remote code risk
BTCPay Server's Nov. 18 emergency update fixes five nginx flaws, including unauthenticated remote code execution, while operators also confront an earlier wallet-drain alert.

Outputs
Nov. 18: BTCPay Server issued an emergency update for five nginx vulnerabilities.
CVE-2026-123007 can enable unauthenticated remote code execution when HTTP/2 is enabled.
nginx 1.30.7 and 1.31.9 contain the fixes; each release has 10 security fixes in total.
The temporary workaround disables HTTP/2 inside the nginx container.
BTCPay Server 2.4.1 and earlier were targeted in the earlier wallet-theft incident; version 2.4.2 shipped Aug. 7.
BTCPay Server issued an emergency update on Nov. 18 for five nginx vulnerabilities, including CVE-2026-123007, which can let a remote attacker execute code without authentication on installations with HTTP/2 enabled.
The project said in a pinned post on X that the update covers five flaws disclosed by security researchers under the NGINX2Root name. Security researcher Brian Pak announced the disclosure on Nov. 18.
BTCPay Server urged operators to install the fix “as soon as possible,” while the bundled nginx fixes ship in version 1.30.7 on the stable branch and 1.31.9 on the mainline branch.
What does the emergency update change for operators?
It changes the remediation sequence for every standard deployment: operators must patch the nginx layer, and those unable to update immediately must disable HTTP/2 temporarily. Because nginx handles inbound traffic before requests reach BTCPay Server, the vulnerable component sits on the payment operation’s connection path. The fix therefore addresses infrastructure exposure, not only an application feature.
Administrators with dashboard access can open Server Settings, select Maintenance and click Update, according to the project’s server FAQ. Docker operators can sign in to the host over SSH, switch to a root shell, open the btcpayserver-docker directory and run the btcpay-update.sh script.
The script pulls the latest changes from the branch the operator has checked out, saves available container logs and recreates the services. The updater keeps the five most recent successful log captures. Each archive records what was available at capture, so operators checking whether the update completed must also inspect the current state of the services.
Operators unable to update immediately should follow 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 include fixes beyond HTTP/2.
Users relying on Umbrel or Start9 should install the update when their platform makes it available, leaving the timing to each platform’s release schedule.
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 project’s networking guide identifies nginx as the handler for incoming connections on standard web and HTTPS ports.
The nginx release notice lists fixes for all five issues in both open-source releases. Two affect HTTP/2; the remaining three concern HTTP/3, the resolver and the mail proxy module. The stable and mainline versions each contain 10 security fixes in total, including the five in BTCPay Server’s announcement.
The researchers said a separate Linux kernel vulnerability could combine with an nginx flaw to gain root access, the highest privilege level on the host. That chain turns a web-layer flaw into a host-level security event, raising the operational stakes for payment installations.
An earlier wallet-drain alert targeted older releases
A Nov. 2 crypto.news report said BTCPay Server had urged operators to shut down payment servers after reports of funds being taken from Bitcoin hot wallets on older installations. The project’s incident report said the reports involved Bitcoin and Litecoin and identified BTCPay Server 2.4.1 and earlier as the targeted versions.
The project dated the relevant fix to Aug. 7, when it released version 2.4.2. It received the first theft report by email on Nov. 1 and contacted hosting providers, including LunaNode, asking them to take affected instances offline as a precaution. By then, several security updates had followed the August fix.
The incident report said the project had seen no impact from the reported attacks on servers already running 2.4.2 or later when the warning went out.
For operators still running older installations, the project recommended moving to a fresh server with a new wallet. That advice applied even if an operator saw no theft or updated the existing server after the warning. Affected operators were asked to preserve logs and transaction records before replacing the old server.
The immediate priority is to verify that every instance runs the patched nginx release or has HTTP/2 disabled. For Umbrel and Start9 installations, the platform release date determines when the remediation reaches the node.
via crypto.news (Source)
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