Latest News

BTCPay Issues Emergency Patch for Five Nginx Security Flaws

BTCPay Server has released an emergency security update addressing five vulnerabilities in Nginx that could allow unauthenticated attackers to execute malicious code on servers used by merchants to process Bitcoin payments.

The open-source payment platform announced the update on November 18, 2026, urging operators to install the patched Nginx version 1.31.9 as soon as possible. The vulnerabilities affect the web server and reverse-proxy software used in BTCPay deployments, rather than Bitcoin’s underlying network.

According to a November 18 advisory from the European Union’s cybersecurity response team, CERT-EU, researchers successfully demonstrated exploitation of one vulnerability. However, neither CERT-EU nor BTCPay had reported confirmed attacks exploiting the newly disclosed Nginx flaws at the time of their announcements.

How Serious Are the Five Nginx Vulnerabilities?

The emergency update addresses five vulnerabilities identified as CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425.

CERT-EU assigned each vulnerability a CVSS severity score of 8.1, warning that exploitation could permit remote code execution with the privileges of an Nginx worker process.

One of the most consequential flaws, CVE-2026-123007, involves memory corruption in HTTP/2 flow control. An attacker could exploit the weakness remotely without authentication when HTTP/2 is enabled on a vulnerable server.

A second HTTP/2 vulnerability, CVE-2026-123633, involves a use-after-free condition during connection draining and upstream server communication. The remaining flaws affect HTTP/3 processing, DNS resolution and mail-proxy authentication under specific configurations.

Successful exploitation could compromise the web-facing infrastructure supporting a payment application. Depending on the server’s configuration and the attacker’s subsequent access, that could threaten payment availability, application integrity or sensitive information.

However, remote execution within an Nginx worker process does not automatically establish access to cryptocurrency private keys or administrative control over the entire host.

Investor Takeaway

The immediate risk concerns internet-facing payment infrastructure rather than Bitcoin itself. For merchants operating their own servers, a compromise could interrupt payment processing or expose connected systems, although no losses have been attributed to these five vulnerabilities.

What Should BTCPay Server Operators Update?

BTCPay said operators can apply the security fix through the Server Settings and Maintenance section of their installations. Administrators managing Docker deployments can alternatively use the project’s standard update script.

Users running BTCPay through node platforms such as Umbrel or Start9 were advised to install the update once their respective platforms make it available.

The patch upgrades the underlying Nginx dependency to version 1.31.9. It does not represent a new version of the BTCPay application itself, meaning administrators should verify the Nginx component rather than relying exclusively on the application version number.

Nginx separately released patched stable version 1.30.7 and mainline version 1.31.9 on November 18, addressing ten security vulnerabilities across its software.

For installations that cannot be updated immediately, BTCPay pointed to a temporary workaround involving disabling HTTP/2. CERT-EU confirmed that this measure mitigates the two HTTP/2 vulnerabilities but does not resolve all five flaws.

The distinction matters because the security exposure depends on both the installed software version and the services enabled on the server.

How Does the Warning Compare With Earlier BTCPay Attacks?

The latest disclosure follows two security incidents involving BTCPay installations earlier in 2026, although the Nginx vulnerabilities are separate from those previously exploited.

In August, attackers exploited a BTCPay Server vulnerability that exposed administrative credentials used by Lightning Network Daemon (LND) nodes. The credentials, known as macaroons, could allow unauthorized control of affected Lightning nodes.

As FinanceFeeds reported, the incident prompted BTCPay to restrict certain remote Lightning connections and release version 2.4.2 to close the vulnerability and regenerate credentials.

The attacks affected Lightning-related infrastructure rather than ordinary on-chain Bitcoin wallets, and several operators reported that their Lightning funds had been stolen.

In August, BTCPay supporters also established a recovery initiative offering rewards of up to 3 BTC for efforts to recover stolen funds.

A further security warning emerged in November after operators reported unauthorized withdrawals from Bitcoin and Litecoin hot wallets running outdated BTCPay software.

BTCPay’s investigation identified an attack vector affecting installations running version 2.4.1 or earlier. The project had not established the precise mechanism of unauthorized administrative access, and no total loss figure was disclosed.

FinanceFeeds covered the November hot-wallet incident, including the distinction between installations retaining private keys on their servers and watch-only configurations requiring external transaction signatures.

Investor Takeaway

The repeated incidents demonstrate how merchant-controlled payment infrastructure can face risks involving both application vulnerabilities and external software dependencies. Self-hosting removes reliance on a centralized payment processor but transfers responsibility for software maintenance, access controls and wallet security to individual operators.

What Are the Financial Implications for Bitcoin Merchants?

BTCPay Server allows merchants to accept Bitcoin and Lightning Network payments without relying on a conventional custodial payment processor. Its self-hosted architecture gives businesses control over transaction processing and wallet integration.

That operating model also creates different risk profiles depending on how funds are stored. Servers holding hot-wallet credentials may face greater potential financial exposure following a compromise than configurations requiring transaction signatures from separate devices.

For businesses processing cryptocurrency payments, the consequences of an infrastructure breach can extend beyond direct theft to transaction interruptions, delayed settlement and the costs of investigating compromised systems.

BTCPay has not disclosed evidence that the newly identified Nginx vulnerabilities have caused customer losses, nor has it quantified how many installations remain unpatched.

The immediate financial exposure therefore cannot be calculated from the available disclosures. The priority for operators is to confirm that vulnerable Nginx components have been replaced and that their payment infrastructure remains protected against unauthorized access.

You may also like