BTCPay Server Issues Emergency Update for Five Nginx Flaws, Including Unauthenticated Remote Code Execution
Published November 19, 2026, 2:10 PM PKT. Based on BTCPay Server's November 18, 2026 announcement (primary source, quoted via Cointelegraph and crypto.news), with corroboration from Cointelegraph, crypto.news and the CERT-EU advisory as secondary sources.
BTCPay Server issued an emergency update on November 18, 2026, fixing five vulnerabilities in nginx, the web server software that routes incoming traffic to its self-hosted Bitcoin ($BTC) payment application, and urged operators to install the fix as soon as possible. The update installs nginx version 1.31.9. The most serious flaw, CVE-2026-123007, affects servers with HTTP/2 enabled and can let a remote attacker run code on the machine without logging in, according to the researchers who disclosed the flaws under the name NGINX2Root.
The five flaws, and the one that needs no login
BTCPay Server listed five flaws in its announcement: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425. Security researcher Brian Pak announced the NGINX2Root disclosure on November 18. Two of the vulnerabilities affect HTTP/2, and the remaining three concern HTTP/3, the resolver and the mail proxy module, according to crypto.news. Nginx released fixes in version 1.30.7 on its stable branch and 1.31.9 on its mainline branch, and each release contains 10 security fixes in total, including the five named in BTCPay Server's announcement. The researchers said a separate Linux kernel vulnerability could be combined with an nginx flaw to gain root access, the highest level of privilege on the host. The scale of the exposure is large: a Shodan survey published on November 10 and cited by security firm Xint counted 56.7 million hosts running nginx.
The European Union's cybersecurity response team, CERT-EU, said in a Wednesday advisory that the flaws could allow attackers to remotely run malicious code on vulnerable servers without logging in. Researchers demonstrated how to exploit one vulnerability, but CERT-EU said no attacks involving any of the five flaws were reported as of Wednesday, according to Cointelegraph. That distinction matters: the danger is demonstrated, not yet observed in the wild, but every unpatched BTCPay Server with HTTP/2 enabled is reachable by the same path the researchers used.
How operators install the fix
BTCPay Server gave separate instructions for each way operators run the software. Administrators who manage their servers through the web dashboard can open Server Settings, select Maintenance and click Update, according to the project's server FAQ. Operators running a Docker installation from the command line can sign in to the host over SSH, switch to a root shell, open the btcpayserver-docker directory and run the project's btcpay-update.sh script. Users running BTCPay Server through a node platform such as Umbrel or Start9 were told to install the update when their platform makes it available.
Operators who cannot update immediately have a temporary workaround. In a follow-up post, BTCPay Server directed them to guidance from core contributor @ndeet: disable HTTP/2 inside the nginx container and reload nginx after checking the configuration. The contributor described the change as temporary, and it is only a partial shield. According to Xint's findings, disabling HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633, but not the other three flaws, which concern DNS resolution, HTTP/3 backends and mail proxying.
A different flaw from the November wallet thefts
The nginx flaws are not connected to the hot-wallet thefts BTCPay Server reported earlier in November. Those thefts involved a separate vulnerability in BTCPay Server 2.4.1 and earlier, with the fix dated to August 7, when version 2.4.2 was released. On November 2, BTCPay Server urged operators to shut down payment servers after reports of funds being taken from Bitcoin and Litecoin ($LTC) hot wallets on older installations, and a Bitquery trace later put the theft at $1.63 million across 682 sweeps. Cointelegraph noted the emergency update follows two earlier incidents: in August, attackers exploited a flaw to obtain credentials for Lightning Network nodes and steal funds, and in November, BTCPay reported the hot-wallet thefts on outdated software, saying attackers had used a different method to exploit the August flaw. The nginx update fixes the web server in front of the payment application, not the wallet software itself.
What happens next
Operators who delay the update leave a public-facing server exposed to unauthenticated code execution, and the HTTP/2 workaround does not patch the other three flaws. The next signals to watch are whether CERT-EU or BTCPay Server reports any exploitation in the wild, and when Umbrel and Start9 ship the update to the operators who depend on their release schedules. Until then, the project's own advice is blunt: update as soon as possible.
This article is news reporting and is not investment advice.
Sources
- BTCPay Server (@BtcpayServer), X post, November 18, 2026 (primary source: emergency update announcement listing the five flaws, CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425, urging operators to update as soon as possible; post text quoted via Cointelegraph and crypto.news)
- Cointelegraph, BTCPay Server Issues Emergency Update for 5 Security Flaws, November 19, 2026 (secondary source: update installs nginx version 1.31.9; CERT-EU Wednesday advisory says the flaws could allow attackers to remotely run malicious code without logging in; researchers demonstrated how to exploit one vulnerability, with no attacks involving any of the five flaws reported as of Wednesday; operators can install the fix through maintenance settings or Docker; node platform users update when their platforms make it available; August Lightning node credential theft and November hot-wallet thefts involved separate flaws)
- crypto.news, BTCPay Server issues emergency update for five nginx flaws, November 19, 2026 (secondary source: nginx released fixes in version 1.30.7 on its stable branch and 1.31.9 on its mainline branch; Docker operators who cannot update immediately were pointed to a workaround that turns off HTTP/2; Umbrel and Start9 users were told to install the update when their platform makes it available; security researcher Brian Pak announced the NGINX2Root disclosure on November 18; a separate Linux kernel vulnerability could be combined with an nginx flaw to gain root access; two vulnerabilities affect HTTP/2 and the remaining three concern HTTP/3, the resolver and the mail proxy module; the stable and mainline releases each contain 10 security fixes in total; the November 2 hot-wallet warning involved BTCPay Server 2.4.1 and earlier, with the fix dated August 7 in version 2.4.2)
MABOnChain Daily Brief
The key crypto and markets stories in one short, plain-language email. Free. Unsubscribe any time.
Prefer chat? Join us on Telegram Watch on YouTube
Keep reading
Six Senators Press Treasury to Give State Stablecoin Issuers Equal Footing Under the GENIUS Act
Six bipartisan senators led by Cynthia Lummis and Kirsten Gillibrand wrote to Treasury Secretary Scott Bessent on November 18, 2026, urging the Treasury to extend the GENIUS Act safe harbor to state-supervised stablecoin issuers. The senators warned that the Treasury's proposed rule, which protects issuers with pending federal applications but offers no equivalent for state issuers, could push firms toward federal licenses through the Office of the Comptroller of the Currency, the opposite of what Congress intended when it wrote the law.
Court Docs Show Binance Hackers Took 192 Tokens Across 11 Networks, $3.46 Billion in Stablecoins
Court documents filed in Abu Dhabi show the hackers behind the October 29, 2026 Binance theft took 192 cryptocurrencies across 11 blockchain networks, worth about $6.3 billion. Stablecoins accounted for at least $3.46 billion of the haul, led by $2.50 billion in Tether ($USDT) and $826 million in USD Coin ($USDC), while Bitcoin ($BTC) was the second largest single loss at $1.42 billion. The Abu Dhabi court will decide on December 1 whether to extend a $6.5 billion worldwide freezing injunction and whether firms holding frozen assets must hand them over.
Pearl Jumps 26% as FP8 Testnet Upgrade Nears and Price Closes In on All-Time High
Pearl ($PEARL) rose about 26% to $2.33 on November 19, 2026, closing within about 5% of its $2.46 all-time high, as a scheduled FP8 upgrade reached the project's testnet, Coinbase opened spot and perpetual futures trading on November 13, and NEAR Intents reported $10 million in PEARL flows. Trading volume hit about $59 million, more than five times its 30-day median, while Bitcoin ($BTC) fell.
Three DeFi Exploits Drain About $5.4 Million in a Single Day
Three unrelated DeFi projects were drained on November 18, 2026. K3 Capital's sBOLD vault lost about $3.43 million in roughly eight minutes, Gonka's Ethereum bridge lost about $1.05 million after an attacker swapped its signing key, and Reental lost up to about $955,000 after an admin key rewrote its lending markets. Blockaid flagged all three, and none of the three had published a full explanation by the morning of November 19.



