afc2b4f6-e
BTCPay Server Rushes Patch for Five nginx Flaws
BTCPay Server is rushing an urgent patch for five nginx vulnerabilities, including an unauthenticated HTTP/2 remote code execution flaw affecting 98.9% of version-identifiable nginx servers.

Outputs
BTCPay Server is preparing an urgent update for five nginx vulnerabilities.
The most severe flaw affects nginx's HTTP/2 implementation and allows remote code execution without authentication.
Researchers trace the HTTP/2 vulnerability to 2015 and estimate 98.9% of version-identifiable nginx servers run affected software.
Combining the HTTP/2 flaw with a separate Linux kernel vulnerability could give attackers root access to host servers.
BTCPay Server urged administrators to install the update promptly.
BTCPay Server, the open-source project behind self-hosted cryptocurrency payment software, is preparing an urgent update to remediate five vulnerabilities in nginx, including an HTTP/2 flaw that researchers say enables remote code execution without authentication.
The severity of the HTTP/2 bug sits at the center of the disclosure. Researchers trace the vulnerability back to 2015 and estimate that 98.9 percent of nginx servers running identifiable software versions operate affected code. Put differently, nearly every nginx deployment that exposes its version information has shipped with the flaw for roughly a decade.
Why this matters for merchants
BTCPay Server supplies merchants with self-hosted payment infrastructure for accepting Bitcoin (BTC) and other cryptocurrencies. Unlike hosted payment processors, the software runs on servers the merchant or its integrator controls, which places patching responsibility squarely with each administrator.
That architecture is precisely why the project urged administrators to install the update promptly. A merchant running an unpatched instance does not merely risk a service disruption; in the worst case, it risks the host machine itself.
Researchers say that combining the HTTP/2 flaw with a separate Linux kernel vulnerability could grant an attacker root access to the host server. Root access means broad control over the machine — the ability to read keys, alter payment data, or pivot to other systems on the same network.
What does this change for operators?
Three operational points follow from the disclosure.
- Attack surface without authentication. The HTTP/2 flaw allows code execution without valid credentials. Any service exposed to the internet that terminates HTTP/2 through an affected nginx build qualifies as a target.
- A decade of exposure. A flaw dating to 2015 implies that long-running, stable deployments — often the ones merchants consider safest — are affected.
- Escalation path. The documented combination with a kernel-level bug means a compromised nginx process is not the end of the incident; it can become a full host takeover.
For payment operators, the practical sequence is direct: apply the BTCPay Server update when it lands, verify the underlying nginx version, and review whether the host kernel also carries the referenced kernel vulnerability. Patching the application layer alone leaves the escalation path open.
The patch window
BTCPay Server has not publicly attached a fixed release date to the update, describing it as urgent and asking administrators to move quickly once it ships. Administrators who cannot patch immediately should treat exposure review — restricting unauthenticated HTTP/2 reachability where feasible — as an interim measure while the update is pending.
The rollout of this patch, and the speed with which self-hosted merchants apply it, will determine whether a decade-old nginx flaw becomes an incident in payment infrastructure rather than a disclosure.
via tokenpost.com (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,574 articles