On this page (6 sections)
CVE-2026-119757 is a critical information disclosure flaw in BTCPay Server. According to the NVD record, versions before 2.4.2, including 2.4.2 release candidates, let unauthenticated remote attackers retrieve .macaroon credential files for an LND (Lightning Network Daemon) node.
A macaroon is the credential LND uses to authorize actions. If one with enough permissions leaks, whoever holds it can act as the node owner. Anyone running a self-hosted BTCPay Server connected to LND, including merchants, agencies and hosting administrators who manage such stores, should treat this as urgent.
What the vulnerability does
The NVD description says an attacker needs no login. They can reach and download the .macaroon files that an LND node uses as credentials. The record states that an exposed macaroon can give full control of the LND node, including moving funds, and that this results in theft of funds from affected deployments.
The two weakness classes fit that picture. CWE-552 covers files or directories that are accessible to parties who should not reach them. CWE-522 covers credentials that are not adequately protected. Put together, a secret file that should stay private on the server becomes retrievable over the network.
Who is realistically exposed
The flaw concerns BTCPay Server deployments that use an LND node. Stores that use other payment backends are not described as affected in the record, though you should still update. The risk is highest when the server is reachable from the internet, which is the normal setup for a store accepting payments.
The impact goes beyond a website outage or a leaked customer list. The record describes loss of control over the Lightning node and its funds. If your node holds a meaningful balance or channels, a leaked macaroon is a financial incident, not just a data exposure.
How to check your exposure
Start by identifying the BTCPay Server version you run. In the web interface, the version is typically shown in the server settings or footer. If you deployed with the standard Docker-based setup, you can also check which images are running. This read-only command lists running containers and their image tags on the host, so look for the BTCPay Server image and compare its tag with 2.4.2:
docker ps --format '{{.Names}} {{.Image}}'If you cannot confirm that you run 2.4.2 or later, assume you are affected. Also review your web server and reverse proxy access logs for unexpected requests that ask for files ending in .macaroon. This grep is read-only and prints matching log lines; adjust the log path to your setup:
grep -i 'macaroon' /var/log/nginx/access.log*A hit with a successful response is a strong sign the file may have been fetched. No hits does not prove safety, because logs can be rotated, disabled or incomplete.
What to do now
- Confirm your BTCPay Server version and plan an upgrade to 2.4.2 or later (verify the fixed release in the vendor advisory).
- Read the BTCPay Server and VulnCheck advisories linked above for any extra steps or workarounds.
- Back up your configuration and wallet data before upgrading, following the vendor's documented procedure.
- After upgrading, assume previously reachable macaroons may be compromised and rotate your LND credentials according to LND documentation.
- Check your LND node for unexpected channel activity, payments or new channels, and compare against your own records.
- If you see unauthorized movement of funds, stop relying on the node, preserve logs, and contact your incident support channel.
- Limit who can reach the server: restrict admin and node-related endpoints at the reverse proxy or firewall where you can.
- Keep access logs long enough to investigate later.
Updating the software closes the hole going forward, but it does not undo a leak that already happened. A macaroon that was downloaded before the fix remains valid until you rotate it, so credential rotation is the step people most often skip.
Detection and monitoring afterwards
Watch your node for outbound payments, channel closures or new channels you did not initiate. Alert on any access to credential-like paths in your web server logs. If your store sits behind a reverse proxy, make sure it only exposes the routes the application needs.
From the outside, you can run an external review of your public site with the Webforta scanner to spot exposed services and misconfigurations you may have forgotten about, and use certificate and header monitoring to notice unexpected changes. These help with general hygiene; they are not a substitute for patching, and we do not claim they detect this specific flaw.
For broader reading on protecting a payment-taking site, see security for online stores and the small business website security guide. A web application firewall can add a layer of filtering, but it should not replace updating.
What is still unknown
- Whether the flaw has been exploited in the wild. The research does not say.
- The exact conditions and file locations involved, which are in the referenced advisories we could not read.
- Whether any workaround exists short of upgrading.
- Only one independent publisher covers this story so far, so details may change as more analysis appears.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
