# CVE-2026-119757: BTCPay Server < 2.4.2 LND Macaroon Credential File Disclosure


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-87gv-mpgp-xpp2

## What is CVE-2026-119757?

CVE-2026-119757 is a critical vulnerability in BTCPay Server, published on 5 Nov 2026. 

### Official description

BTCPay Server before 2.4.2, including 2.4.2 release candidates, contains an information disclosure vulnerability that allows unauthenticated remote attackers to retrieve .macaroon credential files for an LND (Lightning Network Daemon) node. Attackers can use the exposed macaroon to gain full control of the LND node, including moving funds, resulting in theft of funds from affected deployments.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-119757?


## How do I fix CVE-2026-119757?

No fix has been published for CVE-2026-119757 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119757 being exploited?

There is no known exploitation of CVE-2026-119757 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119757 and fix it if it is affected.

What it is: CVE-2026-119757 is a critical vulnerability in BTCPay Server, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119757 in the wild and no public exploit code.

Affected product: BTCPay Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119757/ (Markdown: https://insights.sbomify.com/CVE-2026-119757/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119757
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119757
- OSV: https://osv.dev/vulnerability/CVE-2026-119757

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119757/
Summaries are generated and may contain mistakes; the official description above is the record.