BTCPay Server ships emergency update for five NGINX code-execution flaws

- BTCPay Server issued an emergency update on November 18 to patch five NGINX vulnerabilities, including one that lets an unauthenticated attacker run code on servers with HTTP/2 enabled.
- Because the software is self-hosted, merchants must apply the fix themselves, and a temporary HTTP/2 workaround covers only two of the five flaws.
- The alert is separate from the November 1 hot-wallet thefts that cost merchants about $1.63 million.
On November 18, BTCPay Server issued an emergency update to fix five security vulnerabilities in NGINX. Depending on the configuration of the server, the flaws could allow attackers to execute commands without having to log in. Merchants that operate their own BTCPay servers are responsible for upgrading the affected system.
The vulnerabilities are in NGINX, a solution that enables the management of inbound online traffic, and are not related to either Bitcoin or BTCPay’s wallet software. The recently discovered vulnerabilities have nothing to do with the hot wallet thefts reported earlier this month.
Five NGINX flaws, one unauthenticated path to remote code execution
BTCPay listed five CVEs: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425. Security firm Xint explained their different attack conditions in its November 18 nginx2root research.
Out of all five vulnerabilities, CVE-2026-123007 has the potential to impact the highest number of servers. The vulnerability is exploited when HTTP/2 is active on NGINX installations. With this vulnerability, attackers are able to execute instructions without the need to login, being able to use the privileges of the NGINX worker process. The flaw has been in the system since 2015, when NGINX launched HTTP/2 in release 1.9.5.
On November 18, NGINX published versions 1.30.7 (stable) and 1.31.9 (mainline), both of which fixed all five vulnerabilities. BTCPay recommended that system administrators to perform the upgrades via Server Settings or execute its Docker update script using SSH.
Why switching off HTTP/2 only closes part of the door
Merchants that cannot apply the updates immediately can deactivate HTTP/2 using a workaround provided by one of the BTCPay contributors. However, the workaround will not remain operational once the container is replaced.
Xint’s findings indicate that deactivating HTTP/2 will block CVE-2026-123007 and CVE-2026-123633, but not the other three flaws. The three flaws concern DNS resolution, HTTP/3 backends, and mail proxying. The updates still need to be applied.
According to a relevant Shodan survey published on November 10 and referenced in Xint, 56.7 million hosts used NGINX. Of that number, only 11.94 million gave information about their versions, and almost all of them (98.9%) were affected. The above figures cannot confirm vulnerability, owing to the importance of HTTP/2 settings and backported security updates.

A separate theft wave hit older BTCPay servers on November 1
BTCPay’s November 2 advisory identified a separate attack against servers running version 2.4.1 or older. Thieves used a different method to exploit a flaw patched in August.
Bitquery traced 682 Bitcoin and Litecoin hot-wallet sweeps worth about $1.63 million between October 30 and November 2. As Cryptopolitan reported, attackers logged in as administrators, although how they gained access remained unclear.
BTCPay advised affected users to move to fresh servers and wallets. Updating alone cannot undo a compromise.
What downtime and patching could cost cross-border Bitcoin checkout
Even without theft, a disabled checkout can mean lost sales. The stakes are rising as more businesses accept crypto payments.
River’s 2026 report found 74% growth in merchants accepting Bitcoin during 2025. Monthly Lightning Network volume also topped $1 billion.
CoinGate’s H1 2026 report, updated October 5, recorded 782,403 paid orders, up 21.4% year over year—roughly one every 20 seconds. Merchants settled 75.4% of orders in fiat. Payments were concentrated in software, digital services, and cross-border business.
Neither source measures BTCPay transactions. Outages can still cost merchants orders and customer trust, without a demonstrated effect on Bitcoin’s price.
Don’t just read crypto news. Understand it. Subscribe to our newsletter. It's free.
FAQs
What did BTCPay Server patch on November 18?
It released an emergency update addressing five NGINX vulnerabilities (CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425) and told admins to update immediately.
Does disabling HTTP/2 fully protect a BTCPay server?
No. According to Xint, turning off HTTP/2 blocks two of the flaws, CVE-2026-123007 and CVE-2026-123633, but leaves the other three open, so only updating to NGINX 1.30.7 or 1.31.9 is a complete fix.
Is this emergency update related to the November 1 hot-wallet thefts?
No. The November 1 thefts, which Bitquery traced to about $1.63 million drained from BTCPay 2.4.1 and earlier, involved admin logins to older servers and are separate from the newly disclosed NGINX flaws.
Disclaimer. The information provided is not trading advice. Cryptopolitan.com holds no liability for any investments made based on the information provided on this page. We strongly recommend independent research and/or consultation with a qualified professional before making any investment decisions.

Ibiam Wayas
Ibiam Wayas has covered the crypto news beat since 2019. He studied Computer Science at National Open University of Nigeria. His work has appeared on various crypto news platforms, including Coinfomania, Crypto News Australia, and AltcoinBuzz. Drawing on his background in Computer Science, he now focuses on crypto, robotics, and longevity news.















