544d5d2c-6
BTCPay urges emergency nginx patch for CVE-2026-123007 command flaw
BTCPay Server moved operators to emergency nginx updates after Xint disclosed five flaws, including CVE-2026-123007, an unauthenticated command-execution bug. Node platforms have yet to publish.

Outputs
Xint disclosed five nginx flaws; CVE-2026-123007 allows unauthenticated command execution with worker-process permissions when HTTP/2 is enabled.
The remaining findings cover a second HTTP/2 flaw, HTTP/3, the DNS resolver and the mail proxy.
Upstream fixes ship in nginx stable 1.30.7 and mainline 1.31.9; disabling HTTP/2 blocks only two of the five flaws.
BTCPay's Nov. 2 incident report tied Bitcoin and Litecoin hot-wallet thefts to versions 2.4.1 and earlier, with the fix shipped Aug. 7 in version 2.4.2.
BTCPay says no attacks using the referenced nginx exploits have been publicly confirmed so far.
An unauthenticated attacker can execute commands with the nginx worker process's permissions on a BTCPay Server, according to Xint, the research team that disclosed the flaws. The bug, tracked as CVE-2026-123007, requires HTTP/2 to be enabled on an affected server.
Xint disclosed five nginx flaws in total. Beyond CVE-2026-123007, the findings cover a second HTTP/2 flaw, HTTP/3, the DNS resolver and the mail proxy, each affecting different configurations. BTCPay Server, the self-hosted Bitcoin and Litecoin payment platform, published emergency update instructions in response.
BTCPay said it understood that no attacks using the referenced nginx exploits had been publicly confirmed so far. Operators are therefore patching ahead of any confirmed campaign rather than after one.
How do I patch BTCPay Server right now?
BTCPay published three routes, and the right one depends on how the server is deployed.
- Web dashboard. Server administrators open Server Settings → Maintenance → Update.
- Docker over SSH. Log in to the host, switch to a root shell with
sudo su -, enter thebtcpayserver-dockerdirectory and runbtcpay-update.sh. - Node platforms. Users of Umbrel, Start9 and similar platforms install the update as soon as their platform makes it available.
The Docker updater pulls the latest changes from the checked-out branch and recreates the services. To verify the result, run docker exec nginx nginx -v. The expected output reads nginx version: nginx/1.31.9.
What if nginx runs outside the Docker stack?
For separately managed nginx installations, the upstream release notice lists fixes in stable version 1.30.7 and mainline version 1.31.9. Distribution packages may instead backport the fixes. Xint advises checking the full package version against the distribution's advisory and restarting nginx after installation, rather than only reloading the configuration.
Does turning off HTTP/2 protect the server?
BTCPay also endorsed a temporary workaround from core contributor @ndeet for Docker operators who cannot patch immediately. The nonpersistent workaround changes http2 on to http2 off in the default nginx configuration file, tests the configuration and reloads it if the test passes.
Operators running custom configurations should follow Xint's guidance to disable HTTP/2 on every affected listener, including legacy listen settings. The catch is narrow in scope: Xint cautions that disabling HTTP/2 blocks only two of the five flaws, not the other three. The workaround covers the HTTP/2 path, while the HTTP/3, DNS resolver and mail proxy findings stay reachable on affected configurations.
What does this change for operators holding wallet keys?
The alert follows this month's shutdown warning after reports of Bitcoin and Litecoin thefts from hot wallets, which hold spending keys on the server. BTCPay's Nov. 2 incident report said those attacks targeted BTCPay 2.4.1 and earlier, exploiting a vulnerability fixed in version 2.4.2 on Aug. 7.
The Nov. 2 report advised operators still running 2.4.1 or earlier, or who updated from those versions after the Nov. 1 warning, to move to a fresh server with a new wallet, even if no theft was noticed. Recovery steps include sweeping remaining hot-wallet funds, taking the old server offline and replacing potentially exposed credentials.
BTCPay gave the same advice to anyone with stolen funds or signs of unauthorized access, even after updating. The project said updating alone "cannot remove access an attacker may already have gained."
What happens next?
Node platforms have to publish the patched build, and standalone operators have to confirm a full package version rather than a reload. Until both happen, an unpatched host keeps all five flaws in scope.
The structural shift runs larger than a patch. BTCPay's guidance now treats a compromised server as unrecoverable, swapping in a fresh machine, a new wallet and new credentials rather than rotating a password.
via cryptonews.net (Source)
More from Marcus Bennett
Show full bio
Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,512 articles