BTCPay Server rushes out patch for five NGINX flaws that allow no-login code execution
BTCPay Server dropped an emergency update on November 18 after five NGINX vulnerabilities were found that, depending on server setup, let attackers run commands without logging in. NGINX shipped fixes the same day, and self-hosted merchants are on the hook for upgrading. A workaround exists, but it only blocks two of the five flaws.
- Original source: cryptopolitan.com.
- The source published it on Nov 18, 2026 at 11:03 PM.
- No second outlet has reported it yet. Treat it as a single-source claim.
BTCPay Server issued an emergency update on November 18 to close five security holes in NGINX, the software that manages inbound web traffic. Depending on how a server is configured, the flaws could let an attacker execute commands without logging in. Merchants running their own BTCPay servers have to apply the upgrade themselves.
The five CVEs are CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425. Security firm Xint laid out the different attack conditions in its November 18 nginx2root research. The most dangerous of the bunch, CVE-2026-123007, hits when HTTP/2 is switched on: attackers can run instructions without authentication, using the privileges of the NGINX worker process. That flaw has been sitting in the code since 2015, when NGINX introduced HTTP/2 in release 1.9.5.
NGINX published versions 1.30.7 (stable) and 1.31.9 (mainline) on November 18, both of which fix all five vulnerabilities. BTCPay told administrators to upgrade through Server Settings or run its Docker update script over SSH. For merchants who can't patch right away, a BTCPay contributor supplied a workaround that switches off HTTP/2 — but it blocks only CVE-2026-123007 and CVE-2026-123633, according to Xint, leaving the three flaws tied to DNS resolution, HTTP/3 backends and mail proxying wide open. The workaround also stops working once the container is replaced.
A Shodan survey published November 10 and cited in Xint's research counted 56.7 million hosts running NGINX. Only 11.94 million of them disclosed version information, and 98.9% of those were affected. Those figures can't confirm who is actually vulnerable, since HTTP/2 settings and backported security updates change the picture.
This is a separate problem from the hot-wallet attacks BTCPay flagged in a November 2 advisory, which targeted servers running version 2.4.1 or older. Thieves used a different method to exploit a flaw that had been patched in August, and how they got in as administrators is still unclear. Bitquery traced 682 Bitcoin and Litecoin hot-wallet sweeps worth roughly $1.63 million between October 30 and November 2. BTCPay's advice to victims: move to fresh servers and wallets, because updating alone can't undo a compromise.
A dead checkout costs sales even when nothing is stolen, and crypto payments keep spreading. River's 2026 report found 74% growth in merchants accepting Bitcoin during 2025, with monthly Lightning Network volume topping $1 billion. CoinGate's H1 2026 report, updated October 5, logged 782,403 paid orders, up 21.4% year over year — about one every 20 seconds — with 75.4% of orders settled in fiat and payments concentrated in software, digital services and cross-border business. Neither figure tracks BTCPay transactions.
TopicsBTCPay Server · NGINX · Xint · Shodan · Bitquery · River · CoinGate · Bitcoin
Source: cryptopolitan.com
Written by AI from verified reporting.
More stories
- Web3 & Crypto Listing thedefiant.io 0 viewsSunrise plans 24/7 tokenized Anthropic trading on Solana for IPO day
- Web3 & Crypto coinpedia.org 0 viewsCrypto fear gauge drops to 11 with a December Fed hike on the table
- Web3 & Crypto Upgrade thedefiant.io 0 viewsNEAR Governance Votes to Cut Token Issuance Cap to 1.6%
- Web3 & Crypto Upgrade thedefiant.io 0 viewsInjective Holders Greenlight Veyra Upgrade, Mainnet Lands Nov. 24

