How severe is CVE-2019-12999?

CVE-2019-12999 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-12999?

CVE-2019-12999 affects the following packages: github.com/lightningnetwork/lnd (Go). Ecosystems affected: Go.

How do I fix CVE-2019-12999?

Update github.com/lightningnetwork/lnd to 0.7.1-beta or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12999 is resolved across your whole dependency graph.

How do I detect CVE-2019-12999 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lightningnetwork/lnd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-12999 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2019-12999 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2019-12999, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-12999?

CVE-2019-12999 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2019-12999 published, and has it been updated?

CVE-2019-12999 was published on January 31, 2020 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2019-12999 — lnd

HIGH

CVE-2019-12999 is a high-severity (CVSS 7.5) vulnerability in github.com/lightningnetwork/lnd. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/lightningnetwork/lnd — see the affected versions and patch details below.

Improper Access Control in Lightning Network Daemon

Also known asGHSA-78hj-86cr-6j2vGO-2022-0807

Published

Jan 31, 2020

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/lightningnetwork/lnd

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Lightning Network Daemon (lnd) before 0.7 allows attackers to trigger loss of funds because of Incorrect Access Control.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/lightningnetwork/lnd`	all versions	0.7.1-beta`go get github.com/lightningnetwork/lnd@v0.7.1-beta`

Affected Products

1 product · 1 configurations

Application

network daemonlightning

< 0.7

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Lightning Network Daemon (lnd) before 0.7 allows attackers to trigger lo…

lists.linuxfoundation.orgNVDFeb 2020

Report on github.com

github.comGithubSep 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lightningnetwork/lnd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/lightningnetwork/lnd to 0.7.1-beta or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12999 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Lightning Network Daemon (lnd) before 0.7 allows attackers to trigger loss of funds because of Incorrect Access Control.

O3 Security · Impact-Aware SCA

Is CVE-2019-12999 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Weaponization

No Nuclei template or Metasploit module yet. 3 public proof-of-concept references are listed on this page.

Timeline

Disclosed

Jan 31, 2020

First exploit

Feb 3, 2020

3 days after disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2019-12999

GHSA-78hj-86cr-6j2v

GO-2022-0807

References

Advisorygithub.com · v0.7.0 beta Advisorynvd.nist.gov · CVE 2019 12999 Fixgithub.com · master Webgithub.com · chanleakcheck Evidencelists.linuxfoundation.org

Related vulnerabilities

This CVE is high severity; 3 of 3 other CVEs affecting lnd are rated as high or higher (top: critical).

CVE-2024-38359CVE-2022-39389CVE-2022-44797

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2019-12999 — lnd

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2019-12999 in your dependencies?