

BTCPay Server announced an emergency update on Nov. 18 to address five nginx vulnerabilities affecting its Bitcoin payment software deployments. The project urged server operators to install the fix as soon as possible after researchers disclosed the security flaws. Administrators can update their installations through the dashboard or command line, while users of third-party node platforms should follow their providers’ release schedules.
Security researcher Brian Pak announced the disclosure on Nov. 18 under the NGINX2Root name. Among the five flaws, CVE-2026-123007 affects nginx installations that use HTTP/2. It allows a remote attacker to execute code on a vulnerable server without authentication.
Researchers also identified a separate Linux kernel vulnerability that attackers could combine with an nginx flaw. Such a combination could give an attacker root access, the highest level of administrative privilege on the host. The disclosure prompted BTCPay Server to publish emergency installation guidance in a pinned post on X.
The nginx release notice lists patches in versions 1.30.7 and 1.31.9. Each release contains 10 security fixes, including the five vulnerabilities that BTCPay Server identified in its announcement. Two concern HTTP/2, while the other three involve HTTP/3, the resolver and the mail proxy module.
On a standard BTCPay Server Docker installation, nginx receives incoming web requests and routes them to the payment application or other configured services. It also handles connections through the standard web and HTTPS ports. The version numbers in the release notice refer to nginx rather than the Bitcoin payment application.
Administrators who manage their installations through the dashboard can open Server Settings and navigate to the Maintenance section. From there, they can select Update to begin installing the available changes, as outlined in the project's server FAQ.
For Docker users, the project offers a separate command-line procedure. Operators can connect to the host through SSH, switch to a root shell and open the btcpayserver-docker directory. They can then execute the btcpay-update.sh script.
The updater retrieves changes from the operator’s current software branch, saves accessible container logs and recreates the services. It retains the five most recent successful log captures. Since these archives represent earlier snapshots, operators also need to check their running services to establish whether the update completed.
Meanwhile, users who rely on Umbrel or Start9 should follow their respective platforms’ release schedules. BTCPay Server also directed operators facing delays to temporary guidance from core contributor @ndeet. The workaround disables HTTP/2 inside the nginx container and reloads nginx after a configuration check. It does not address every component listed in the release notice.
Read More: Bitcoin Block Packs 11,255 Transactions, Nears 12,239 Record Set in 2015
The nginx warning follows a separate security incident involving older versions of BTCPay Server. On Nov. 1, the project received its first email report of stolen funds. It subsequently contacted hosting providers, including LunaNode, and requested that they take affected servers offline as a precaution.
In its incident report, the project identified BTCPay Server 2.4.1 and earlier as the versions attackers targeted. Reports involved both Bitcoin and Litecoin. The project had addressed the vulnerability behind those attacks on Aug. 7 with version 2.4.2 and had issued several security updates before receiving the theft reports.
BTCPay Server reported no known impact from those attacks on installations already running version 2.4.2 or later when it issued the warning. For operators who still used vulnerable versions on Nov. 1, the project recommended moving to a fresh server and creating a new wallet.
That advice also applied to operators who found no missing funds or upgraded their existing installations after the warning. The project asked affected users to preserve relevant logs and transaction records before replacing their servers.
BTCPay Server's emergency update addresses five nginx vulnerabilities, including a flaw that permits remote code execution without authentication. The project urges operators to install the security patches promptly, while those awaiting platform updates can follow temporary mitigation guidance. Separate recovery instructions remain applicable to installations affected by the earlier wallet theft incident.