BTCPay Server Issues Emergency Patch for Five Critical NGINX Vulnerabilities
Summary: The self-hosted payment processor urges administrators to update NGINX to versions 1.30.7 or 1.31.9 to fix remote code execution flaws, including one exploitable without authentication via HTTP/2. The security alert is distinct from the November 1 hot-wallet thefts that drained approximately $1.63 million from older server instances.
BTCPay Server issued an emergency update on November 18 to address five critical security vulnerabilities in NGINX, the web server software used to manage inbound traffic for self-hosted payment nodes. The flaws, which include a path to unauthenticated remote code execution, require immediate action from merchants who operate their own infrastructure. BTCPay emphasized that these vulnerabilities are contained within NGINX and are not related to Bitcoin protocol issues or BTCPay’s wallet software.
Five CVEs and Remote Code Execution Risk
The update targets five specific Common Vulnerabilities and Exposures (CVEs): CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425. Security research firm Xint detailed the attack conditions in its nginx2root research, noting that CVE-2026-123007 poses the broadest risk. This vulnerability allows an unauthenticated attacker to execute commands with the privileges of the NGINX worker process if HTTP/2 is enabled on the server. The flaw has existed since NGINX introduced HTTP/2 support in release 1.9.5 in 2015.
On November 18, NGINX released versions 1.30.7 (stable) and 1.31.9 (mainline), both of which resolve all five vulnerabilities. BTCPay advised system administrators to perform upgrades via Server Settings or by executing its Docker update script using SSH. Because BTCPay Server is self-hosted, the responsibility for applying these patches lies entirely with the individual merchant or node operator.
Limited Mitigation via HTTP/2 Deactivation
For operators unable to apply updates immediately, a temporary workaround involves deactivating HTTP/2. However, this measure provides incomplete protection. According to Xint’s findings, disabling HTTP/2 blocks only CVE-2026-123007 and CVE-2026-123633. It does not mitigate the other three flaws, which involve DNS resolution, HTTP/3 backends, and mail proxying. Consequently, full patching remains necessary to secure the server environment.
The scale of potential exposure is significant. A Shodan survey published on November 10 and referenced by Xint indicated that 56.7 million hosts used NGINX. Of the 11.94 million hosts that reported version information, 98.9% fell within the affected range. These figures do not confirm active vulnerability, as they do not account for HTTP/2 configuration settings or backported security fixes from Linux distributions.
Distinction From November 1 Theft Incident
The November 18 security alert is separate from a recent wave of thefts targeting older BTCPay Server installations. In early November, attackers exploited a different vulnerability in servers running version 2.4.1 or earlier, gaining administrative access to drain hot wallets. BTCPay’s November 2 advisory identified the affected versions and urged users to migrate to fresh servers, noting that updating alone cannot undo a prior compromise.
Blockchain analytics firm Bitquery traced the impact of that earlier incident, identifying 682 Bitcoin and Litecoin hot-wallet sweeps worth about $1.63 million between October 30 and November 2. While the November 18 NGINX flaws present a new vector for server compromise, they are unrelated to the admin-level exploits used in the recent thefts. Merchants are advised to ensure their systems are fully patched against both the NGINX vulnerabilities and the previously disclosed BTCPay Server flaws to maintain operational security and prevent potential downtime or loss of funds.