How severe is GHSA-78hj-86cr-6j2v?

GHSA-78hj-86cr-6j2v has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-78hj-86cr-6j2v?

GHSA-78hj-86cr-6j2v affects the following packages: github.com/lightningnetwork/lnd (Go). Ecosystems affected: Go.

How do I fix GHSA-78hj-86cr-6j2v?

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 GHSA-78hj-86cr-6j2v is resolved across your whole dependency graph.

How do I detect GHSA-78hj-86cr-6j2v in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lightningnetwork/lnd. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-78hj-86cr-6j2v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-78hj-86cr-6j2v?

O3 pinpoints whether GHSA-78hj-86cr-6j2v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-78hj-86cr-6j2v actively exploited in the wild?

Yes. There are 3 known exploit references for GHSA-78hj-86cr-6j2v, 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.

When was GHSA-78hj-86cr-6j2v published, and has it been updated?

GHSA-78hj-86cr-6j2v was published on May 18, 2021 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-78hj-86cr-6j2v

HIGH

GHSA-78hj-86cr-6j2v is a high-severity (CVSS 7.5) vulnerability in github.com/lightningnetwork/lnd. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-78hj-86cr-6j2v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Access Control in Lightning Network Daemon

Also known asCVE-2019-12999GO-2022-0807

Published

May 18, 2021

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Blast Radius

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

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

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-78hj-86cr-6j2v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-78hj-86cr-6j2v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-78hj-86cr-6j2v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-78hj-86cr-6j2v in your dependencies?

O3 detects GHSA-78hj-86cr-6j2v across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works