BTCPay Server Issues Emergency Update for Five nginx Flaws
Security
Neutral

BTCPay Server Issues Emergency Update for Five nginx Flaws

BTCPay Server on Nov. 18 urged operators to install an emergency update covering five nginx vulnerabilities disclosed under the NGINX2Root name. The flaws include one that can allow unauthenticated remote code execution on servers with HTTP/2 enabled, and researchers say a Linux kernel flaw could be chained with nginx to reach root.

Nov 18, 2026, 08:48 PM3 min read

Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work

What Happened

BTCPay Server announced an emergency update on Nov. 18 to address five nginx vulnerabilities, and urged operators of its Bitcoin payment software to install it as soon as possible. The project said in a pinned post on X that the flaws were disclosed by security researchers under the NGINX2Root name. The five CVEs cited are CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425.

Security researcher Brian Pak announced the disclosure on the same day. The researchers identified CVE-2026-123007 as the most serious of the group for installations with HTTP/2 enabled, saying it can let a remote attacker execute code without authenticating. They also said a separate Linux kernel vulnerability could be combined with an nginx flaw to gain root access, the highest privilege level on a host.

Scope of the nginx Fixes

The nginx release notice lists fixes for all five issues in both open-source release lines. Two of the vulnerabilities affect HTTP/2, and the other three concern HTTP/3, the resolver and the mail proxy module. The stable and mainline releases each contain 10 security fixes in total, of which the five named by BTCPay Server are a subset. The version numbers that matter for operators are 1.30.7 and 1.31.9, which refer to nginx rather than to BTCPay Server itself.

On the standard Docker deployment, nginx sits in front of BTCPay Server and handles incoming connections on the web and HTTPS ports, routing requests to the payment application and other services on the same installation. That placement is why the flaws matter for the payment stack: the exposed component is the web-facing layer, not only the wallet logic.

Update Paths and Verification

The project published separate instructions for three groups. Administrators using the web dashboard can open Server Settings, select Maintenance and click Update. Docker operators working from the command line can sign in over SSH, switch to a root shell, open the btcpayserver-docker directory and run the btcpay-update.sh script, which pulls the latest changes from the checked-out branch, saves available container logs and recreates the services. Users of node platforms were told to follow their platform's release schedule, with Umbrel and Start9 named in the instructions, so their timing depends on when those platforms distribute the fix.

The updater keeps the five most recent successful log captures. The Docker guide notes that a saved archive reflects the state at capture time, so operators confirming that an update completed should check the current running state of the services rather than rely on the archive. Separately, The Defiant reported that the fix updates the nginx dependency rather than BTCPay Server's own version number, and advised Docker operators to confirm that their nginx container runs 1.31.9. Crypto.news, by contrast, framed the action as an update to the BTCPay Server installation itself. Both descriptions point to the same practical step, but operators should verify the nginx version directly instead of inferring it from the BTCPay version.

Interim Mitigation and Prior Incident

For operators who cannot install the update immediately, BTCPay Server pointed to guidance from core contributor @ndeet. The workaround disables HTTP/2 inside the nginx container and reloads nginx after a configuration check. The contributor described it as temporary, and the nginx release notes list fixes in components beyond HTTP/2, so disabling HTTP/2 does not close the full set of issues.

The disclosure follows an earlier incident. On Nov. 2, crypto.news reported that BTCPay Server had urged operators to shut down payment servers after reports of funds being taken from Bitcoin hot wallets on older installations. In that incident report, the project said it had received reports involving Bitcoin and Litecoin and identified BTCPay Server 2.4.1 and earlier as the affected versions. The two events are separate, and the sources reviewed do not establish a link between the nginx flaws and the earlier hot-wallet reports.

Why It Matters

For Traders

Exposure is concentrated in self-hosted merchant payment servers, so direct market impact on Bitcoin or Litecoin prices is unlikely, though operators holding funds in hot wallets face near-term risk until patched.

For Investors

The episode highlights that custody and payment infrastructure carries web-layer attack surface, a factor to weigh when assessing the operational maturity of self-hosted crypto payment tooling.

For Builders

Operators and integrators should pin and verify the nginx version (1.31.9 or the corresponding fixed release) in their containers, since the dependency, not the BTCPay version number, carries the fix.

This article is for information only and is not financial advice. Read the full disclaimer.

Related Articles

Latest News