Witness Block Parsing DoS Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2022-39389: 1.11% estimated exploitation activity in the next 30 days; percentile 65.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Patches A patch is available starting with lnd v0.15.4. Workarounds Nodes can 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. References https://github.com/lightningnetwork/lnd/issues/7096 https://github.com/lightningnetwork/lnd/releases/tag/v0.15.4-beta

Published by the source

18 Nov 2022, 18:50 UTC

Last modified by the source

29 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hc82-w9v8-83pr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-39389

Advisory: Witness Block Parsing DoS Vulnerability
IDs: CVE-2022-39389, GHSA-hc82-w9v8-83pr
Record: https://patchnext.com/advisories/cve-2022-39389 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/lightningnetwork/lnd 0.15.4-beta. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lightningnetwork/lnd: affected < 0.15.4-beta; fixed in 0.15.4-beta

## Suggested inspection (read-only)
- Go github.com/lightningnetwork/lnd: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lightningnetwork/lnd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hc82-w9v8-83pr (GitHub-reviewed advisory GHSA-hc82-w9v8-83pr lists affected ranges: Go github.com/lightningnetwork/lnd >=0 <0.15.4-beta)

Commands are suggestions: review each one before running it.