CVE-2022-39389

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 1.1% (65th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Lightning Network Daemon (lnd) is an implementation of a lightning bitcoin overlay network node. All lnd nodes before version v0.15.4 are vulnerable to a block parsing bug that can cause a node to enter a degraded state once encountered. In this degraded state, nodes can continue to make payments and forward HTLCs, and close out channels. Opening channels is prohibited, and also on chain transaction events will be undetected. This can cause loss of funds if a CSV expiry is researched during a breach attempt or a CLTV delta expires forgetting the funds in the HTLC. A patch is available in lnd version 0.15.4. Users are advised to upgrade. Users unable to upgrade may use the lncli updatechanpolicy RPC call to increase their CLTV value to a very high amount or increase their fee policies. This will prevent nodes from routing through your node, meaning that no pending HTLCs can be present.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
68
EG Risk 68/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 17, 2022

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Sep 8, 2026
Patch available. Sources: github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Witness Block Parsing DoS Vulnerability · Advisory · lightningnetwork/lnd · GitHub

https://github.com/lightningnetwork/lnd/security/advisories/GHSA-hc82-w9v8-83pr
GitHub release Patch Available

lnd v0.15.4-beta

Patch available: lightningnetwork/lnd v0.15.4-beta

https://github.com/lightningnetwork/lnd/releases/tag/v0.15.4-beta
GitHub pull request

mod+build: bump btcd version to v0.23.3 and bump lnd version to v0.15.4-beta

Fix merged in lightningnetwork/lnd PR #7098 on 2022-11-01 — awaiting tagged release

https://github.com/lightningnetwork/lnd/pull/7098
Web page

[bug]: CRITICAL! Unable to process chain reorg / too many witness items to fit into max message size · Issue #7096 · lightningnetwork/lnd · GitHub

https://github.com/lightningnetwork/lnd/issues/7096

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/lightningnetwork/lnd—
  • every version up to 0.15.4-beta: fixed in 0.15.4-beta
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 107 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:28 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  4. 2026-10-21 06:23 UTCEG score recompute
  5. 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  6. 2026-10-19 16:28 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  7. 2026-10-18 16:28 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  8. 2026-10-18 08:28 UTCEG score recompute
  9. 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  10. 2026-10-16 16:35 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  11. 2026-10-15 16:28 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  12. 2026-10-15 10:24 UTCOSV refresh
  13. 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  14. 2026-10-13 16:29 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  15. 2026-10-12 18:48 UTCEG score recompute
  16. 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  17. 2026-10-11 23:12 UTCEG score recompute
  18. 2026-10-11 13:44 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  19. 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  20. 2026-10-09 20:04 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  21. 2026-10-08 16:40 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  22. 2026-10-07 23:45 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  23. 2026-10-06 15:14 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  24. 2026-10-05 17:40 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  25. 2026-10-04 23:19 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
Show 68 more
  1. 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  2. 2026-10-02 16:23 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  3. 2026-10-01 19:47 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  4. 2026-09-30 16:03 UTCEG score recompute
  5. 2026-09-30 15:00 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  6. 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  7. 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  8. 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  9. 2026-09-24 14:00 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  10. 2026-09-24 05:45 UTCOSV refresh
  11. 2026-09-22 14:45 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  12. 2026-09-20 20:13 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  13. 2026-09-19 15:38 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  14. 2026-09-17 19:24 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  15. 2026-09-16 14:05 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  16. 2026-09-15 03:07 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  17. 2026-09-12 14:57 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  18. 2026-09-11 14:50 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  19. 2026-09-11 09:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  20. 2026-09-08 21:57 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  21. 2026-09-07 15:58 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  22. 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  23. 2026-09-05 15:25 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  24. 2026-09-04 22:59 UTCOSV refresh
  25. 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  26. 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  27. 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  28. 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  29. 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  30. 2026-08-30 01:19 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  31. 2026-08-28 21:38 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  32. 2026-08-27 14:22 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  33. 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  34. 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  35. 2026-08-24 14:13 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  36. 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  37. 2026-08-21 23:46 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  38. 2026-08-20 22:52 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  39. 2026-08-19 17:01 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  40. 2026-08-18 13:45 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  41. 2026-08-18 10:06 UTCOSV refresh
  42. 2026-08-17 13:44 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  43. 2026-08-16 14:53 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  44. 2026-08-16 02:11 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  45. 2026-08-15 01:27 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  46. 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  47. 2026-08-12 13:48 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  48. 2026-08-11 13:39 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  49. 2026-08-10 14:08 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  50. 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  51. 2026-08-08 16:34 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  52. 2026-08-07 16:24 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  53. 2026-08-06 13:44 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  54. 2026-08-05 19:15 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  55. 2026-08-04 15:07 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  56. 2026-08-04 10:35 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  57. 2026-08-03 05:27 UTCOSV refresh
  58. 2026-08-02 02:24 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  59. 2026-08-01 04:13 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  60. 2026-07-30 16:25 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  61. 2026-07-30 01:28 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  62. 2026-07-28 15:33 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  63. 2026-07-26 14:52 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  64. 2026-07-25 14:15 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  65. 2026-07-24 14:15 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  66. 2026-07-23 14:16 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  67. 2026-07-23 02:13 UTCEG score recompute
  68. 2026-07-22 23:00 UTCEG score recompute

Frequently asked(5)

What is CVE-2022-39389?
CVE-2022-39389 is a high-severity vulnerability; its CVE record was published on November 17, 2022. Lightning Network Daemon (lnd) is an implementation of a lightning bitcoin overlay network node. All lnd nodes before version v0.15.4 are vulnerable to a block parsing bug that can cause a node to enter a degraded state once encountered. In this degraded state, nodes can continue to make payments…
When was the CVE record for CVE-2022-39389 published?
The CVE record for CVE-2022-39389 was published on November 17, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-39389 actively exploited?
CVE-2022-39389 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-39389?
CVE-2022-39389 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2022-39389?
A fix for CVE-2022-39389 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-39389

Explore →

Is Your Infrastructure Affected by CVE-2022-39389?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.