fdec0e83-1

ConfirmedSecurity712 words4 min decode

BTCPay ships emergency patch for five NGINX vulnerabilities

BTCPay’s Nov. 18 emergency update fixes five NGINX flaws, including an HTTP/2 path to unauthenticated remote code execution on self-hosted merchant servers.

BTCPay Server ships emergency update for five NGINX code-execution flaws
WitnessBTCPay Server ships emergency update for five NGINX code-execution flawsgeralt / pixabay

Outputs

  1. November 18: BTCPay Server released an emergency update for five NGINX CVEs.

  2. CVE-2026-123007 permits unauthenticated commands when NGINX uses HTTP/2.

  3. NGINX 1.30.7 and 1.31.9 fix all five vulnerabilities.

  4. Disabling HTTP/2 blocks two flaws; three others still require patching.

  5. Bitquery tracked 682 Bitcoin and Litecoin sweeps worth about $1.63 million from October 30 to November 2.

BTCPay Server shipped an emergency update on November 18 for five NGINX vulnerabilities. One flaw can let attackers execute commands without logging in. Merchants running their own BTCPay servers must perform the upgrade.

A server administrator can apply the release through BTCPay Server’s Server Settings. The alternative is to run its Docker update script using SSH. Self-hosted operators carry responsibility for the upgrade.

BTCPay said the flaws sit in NGINX, the software used to manage inbound online traffic. They are not related to Bitcoin or BTCPay’s wallet software. The company also said they are separate from the hot-wallet thefts reported earlier that month.

Which five flaws were patched?

BTCPay listed five CVEs, each covering a different set of attack conditions:

  • CVE-2026-123007: Has the potential to affect the most servers because the exploit requires active HTTP/2.
  • CVE-2026-123633: Can be blocked by deactivating HTTP/2, according to Xint.
  • CVE-2026-123634
  • CVE-2026-121810
  • CVE-2026-113425

Security firm Xint explained the vulnerabilities in its November 18 “nginx2root” research. On the CVE-2026-123007 path, attackers can execute instructions without logging in. They can do so with the privileges of the NGINX worker process.

Xint traced the flaw to 2015, when NGINX introduced HTTP/2 in release 1.9.5. The vulnerable code has remained in the system since then, subject to configuration.

NGINX published version 1.30.7 on its stable branch and 1.31.9 on its mainline branch on November 18. Both releases fix all five vulnerabilities. BTCPay told administrators to “perform the upgrades via Server Settings” or execute its Docker update script using SSH.

Why does HTTP/2 only close part of the risk?

Merchants that cannot patch immediately can deactivate HTTP/2. A BTCPay contributor provided that workaround. It works only until the container is replaced.

Xint found that turning off HTTP/2 “will block CVE-2026-123007 and CVE-2026-123633, but not the other three flaws.” Those remaining vulnerabilities concern DNS resolution, HTTP/3 backends and mail proxying. The updates are still required.

A Shodan survey published on November 10 and cited by Xint counted 56.7 million hosts using NGINX. Only 11.94 million reported version information. Almost all of that group, or 98.9%, were counted as affected.

Those figures do not confirm vulnerability. HTTP/2 settings and backported security updates can change the actual exposure of an installation.

Is this the same wallet-theft wave?

A separate theft wave hit older BTCPay servers on November 1. BTCPay’s November 2 advisory identified an attack against servers running version 2.4.1 or older. Attackers 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. Cryptopolitan reported that thieves logged in as administrators. How they gained that access remained unclear.

BTCPay advised affected users to move to fresh servers and wallets. Updating alone cannot undo a compromise. The NGINX release addresses the web-server vulnerabilities, not wallets already exposed through the earlier attack.

What does this change for BTCPay merchants?

It turns patching into an immediate operational task. Self-hosted operators should install the fixed NGINX release through BTCPay’s update path. If they use the HTTP/2 workaround, they still need a full upgrade. Operators hit by the wallet theft require new infrastructure and fresh wallets.

Even without theft, a disabled checkout can mean lost sales. River’s 2026 report found 74% growth in merchants accepting Bitcoin during 2025. Monthly Lightning Network volume also topped $1 billion.

CoinGate’s first-half 2026 report, updated October 5, recorded 782,403 paid orders. That was a 21.4% year-over-year increase, roughly one order 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. Their figures show broader digital-payment activity, not the rate of BTCPay outages. Downtime can still cost merchants orders and customer trust, without any demonstrated effect on Bitcoin’s price.

The immediate deadline is the next container replacement, when the temporary HTTP/2 shutdown will stop working and the full NGINX upgrade becomes necessary.

via cryptonews.net (Source)

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,512 articles