On November 5, 2026, NVD received CVE-2026-119757, an information disclosure flaw in BTCPay Server, the self-hosted Bitcoin payment processor. An information disclosure rated 9.8 is unusual. What leaks here is not ordinary data but the access token for the Lightning node, and with it the ability to move funds.
The vulnerability
| Field | Value |
|---|---|
| CVE | CVE-2026-119757 |
| Product | BTCPay Server |
| Versions | before 2.4.2, including 2.4.2 release candidates |
| Type | Credential file exposure (CWE-522, CWE-552) |
| CVSS 3.1 | 9.8 — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CVSS 4.0 | 9.3 |
| Score source | VulnCheck (CNA) |
| NVD status | Received (not yet analyzed) |
| CISA KEV | no, at the time of writing |
NVD has not published its own assessment or a CPE configuration yet, so both scores are VulnCheck's.
What a macaroon is, and why this matters
LND (Lightning Network Daemon) is the Lightning node implementation BTCPay Server can drive to accept Lightning payments. LND's API doesn't use passwords. It issues macaroons: .macaroon files that act as bearer tokens. Whoever holds the file holds whatever rights it encodes.
According to the NVD description, a remote, unauthenticated attacker can retrieve the .macaroon files of the LND node attached to a BTCPay Server instance. With that macaroon, they get full control of the LND node, including moving funds, which means theft of funds from affected deployments.
Three things stand out:
- No authentication, no user interaction: the vector is
PR:N/UI:N. A reachable instance is enough. - Both CWEs point the same way: CWE-552 (files accessible to external parties) and CWE-522 (insufficiently protected credentials). This isn't an injection. It's a secret file being served where it shouldn't be.
- The impact is financial and final. A Lightning payment or an on-chain transaction can't be reversed. Patching after the fact won't bring the money back.
The description doesn't say which path or endpoint serves the file. For the technical details, read the BTCPay Server and VulnCheck advisories listed in the references.
Affected versions
The NVD description covers BTCPay Server before 2.4.2 and explicitly adds that 2.4.2 release candidates are affected too. The natural reading is that the final 2.4.2 release is the first fixed version, but NVD has no CPE configuration confirming it. The authoritative source is the vendor's BTCPay Server 2.4.2 security advisory.
Watch out for this one: an instance moved to a 2.4.2 RC to try the new release can look up to date. It isn't.
Detection
- Check the exact version of every instance, release candidates included.
- Reverse proxy logs: unauthenticated requests returning binary content or a
.macaroonfile, or any request path containingmacaroon. - LND activity: outgoing payments, channel opens or closes, on-chain transactions nobody initiated.
- Balances of the node and its channels compared with your payment history.
- Connections to the LND API (gRPC or REST) from addresses other than the BTCPay instance.
Mitigation
- Upgrade to BTCPay Server 2.4.2 (final release), following the vendor advisory.
- Treat macaroons as compromised if the instance was exposed before the upgrade. Regenerate them on the LND side so the old ones stop working. Upgrading BTCPay alone does not revoke a macaroon that has already been taken.
- Restrict the LND API: if only BTCPay Server needs to reach it, keep it on the local network or inside the container network.
- Keep the hot balance small: leave only what incoming payments require on the node, and sweep the rest to cold storage regularly.
- After a confirmed compromise, move the remaining funds to a wallet whose keys have never touched the server.
Why continuously monitor your payment infrastructure
BTCPay Server tends to get installed once on a VPS and forgotten as long as payments keep coming in. That's exactly the kind of self-hosted tool that misses an advisory, and here the cost of missing it is measured directly in funds.
With cveo.tech, list your instances and their versions, and get alerted as soon as a critical CVE affects them.