LND Gossip ChannelUpdate Suppression via Validation Barrier Poisoning
Published August 11, 2026
| Affected Product | Affected Versions | Patched Versions |
|---|---|---|
| lnd | < 0.19.0-beta | 0.19.0-beta |
Impact
Any peer, with no prior channel relationship, could suppress a victim lnd node’s processing of
channel_update or node_announcement messages for a targeted short channel
ID (SCID). The gossiper’s validation barrier gates child messages on the
successful completion of their parent channel_announcement validation. An
attacker sends many channel_announcement messages carrying the target SCID
but an incorrect chain_hash; sending each from a different peer bypasses the
recentRejects cache, and every such announcement fails validation. Any
legitimate channel_update for that SCID that arrives while the poisoned
announcements are in flight is bound to the failing parent and is discarded.
Whether a specific legitimate update is caught in that window depends on
timing, so the attack succeeds probabilistically rather than deterministically;
the sustained spam is also observable as a broader gossip DoS.
The victim will see elevated error-log volume in the gossiper. There is no fund-loss path; affected routing-table entries degrade gracefully when stale, and routing failures are the worst observable outcome.
Severity
Scored against the Lightning Labs severity taxonomy (4-dimension rubric):
| Dimension | Score | Reasoning |
|---|---|---|
| Impact | Low | Degraded gossip accuracy for targeted SCIDs. Routing failures may increase, but there is no fund-loss path and the node continues operating normally. |
| Attack Vector | High | Network. Any peer can send channel_announcement messages with no prior channel relationship. |
| Exploitability | Med | Probabilistic. Flooding is reliable, but whether a specific legitimate channel_update is caught in the failing-parent window depends on timing. Running the spam at scale hits a non-trivial fraction of updates. |
| Virality | Low | Per-SCID, per-victim effort. The attack does not propagate through the network. |
Result: T3. Rule 3 (Impact = Low, base T3); no promotion because Virality is not High.
Patches
The issue was fixed in lnd v0.19.0-beta. Users should update to v0.19.0-beta or later to be protected.
Disclosure timeline
- Identified internally by the Lightning Labs security team.
- Fix merged and released in lnd v0.19.0-beta.
- Public disclosure: 2026-08-11.