BTCPay Server nginx Emergency Update Claims Remain Unverified as Operators Are Urged to Check Official Advisories

Daily Feed
BTCPay Server nginx Emergency Update Claims Remain Unverified as Operators Are Urged to Check Official Advisories

BTCPay Server was reported to have issued an emergency update on Nov. 18 for five nginx vulnerabilities. One flaw was said to allow unauthenticated remote code execution when HTTP/2 is enabled. The BTCPay release notes available for review do not confirm the claims, fixed versions or workaround. Operators should check official BTCPay and nginx channels before acting on specific version numbers or configuration changes.

  • Reported risk: CVE-2026-123007, affecting nginx with HTTP/2 enabled.
  • Reported fixes: nginx 1.30.7 on stable and 1.31.9 on mainline.
  • Key caveat: The year of the announcement date and the nginx claims have not been verified here.
  • Separate incident: Earlier wallet-theft reports involved older BTCPay Server versions, not nginx.

What the nginx notice reportedly says

In a standard Docker deployment, nginx handles incoming web connections and routes requests to BTCPay Server or other configured services. A flaw in nginx could expose a server even if the BTCPay application itself is not vulnerable. Deployments differ, so operators should check whether and how their setup uses nginx.

The notice reportedly attributes five vulnerabilities to researchers using the name NGINX2Root. It identifies CVE-2026-123007 as an HTTP/2 flaw that could let a remote attacker run code without signing in. The notice says two of the five issues involve HTTP/2. The others concern HTTP/3, nginx’s resolver and its mail proxy module.

The reported fixes are nginx 1.30.7 for the stable branch and 1.31.9 for the mainline branch. The notice also says each release includes 10 security fixes in total, covering the five vulnerabilities it describes. The other four CVE identifiers and their technical details are not available here. These release claims have not been independently confirmed against nginx’s security advisories.

The researchers reportedly said a separate Linux kernel vulnerability could be combined with an nginx flaw to gain root access, the highest privilege level on a host. No kernel CVE or technical details were provided, so the claim is difficult to assess. The available information also does not show how many installations may be exposed or whether the vulnerabilities have been exploited in the wild.

What operators should verify

Check the official BTCPay announcement and nginx security advisories for the affected configurations, confirmed CVE identifiers and fixed versions. Then identify the nginx package or container running in your deployment and follow the update instructions for that installation type. An application update may not update every separate component.

BTCPay’s release notes describe a maintenance interface that shows live update progress and failure details. It can help operators monitor an update, but it does not prove that a particular nginx package or container received a specific security fix. Check the running component and version after updating.

The reported notice recommends disabling HTTP/2 in the nginx container as a temporary workaround for operators who cannot update. Exact configuration steps are not available here. Even if confirmed, disabling HTTP/2 would address only the reported HTTP/2 exposure. It would not automatically fix the other alleged nginx flaws or the separate kernel issue. Follow deployment-specific instructions from official channels rather than making a change that could disrupt service.

BTCPay’s release notes also describe other security work, including application-level hardening and a runtime update addressing the Brotli decoder vulnerability CVE-2026-111497. That is a separate issue and does not confirm or fix the reported nginx vulnerabilities.

Earlier wallet-theft reports were a separate matter

Crypto.news reported on Nov. 2 that BTCPay Server had warned operators after reports of Bitcoin and Litecoin hot-wallet thefts on older installations. According to the report, BTCPay identified versions 2.4.1 and earlier as targeted and said the fix was released in version 2.4.2 on Aug. 7. The project reportedly received its first theft report on Nov. 1 and contacted hosting providers, including LunaNode, asking them to take affected instances offline as a precaution. The available information does not specify the years for those dates.

BTCPay reportedly said it had seen no impact from the attacks on servers already running version 2.4.2 or later when the warning was issued. Operators who still had older installations at that time were advised to move to a fresh server with a new wallet, even if they had seen no theft or later updated the existing server. They were also advised to preserve relevant logs and transaction records before replacing the old server.

Those reports concern older BTCPay application versions. The nginx notice concerns a separate web-server component. The available information establishes no connection between the two incidents.

Key questions for BTCPay Server operators

  • Is the nginx advisory confirmed?

    The reported notice and technical details have not been verified against the BTCPay release notes or nginx security advisories available here. Confirm the advisory through official project channels before relying on its version numbers or mitigation steps.

  • What should I check in my deployment?

    Find out whether your setup uses nginx, identify the running package or container version, and follow the update guidance for that installation type. Check the component’s version after updating.

  • Does updating BTCPay necessarily update nginx?

    Not necessarily. The application and nginx may be separate components, so check what your specific update changes and confirm the running nginx version afterward.

  • Does disabling HTTP/2 address all five reported flaws?

    There is no evidence that it does. The proposed workaround is described as temporary and relates to the HTTP/2 exposure. Do not treat it as a fix for the other alleged nginx issues or the separate kernel vulnerability.

Further reading

Share this article

Powered by ADBYTES

Advertise smarter.

Adbytes.Media is a transparent advertising network where advertisers reach real audiences and publishers, affiliates & everyday members earn ADBYTES tokens. Join the community and start earning today.

Back to Blog