AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 63 Bitcoin

Merge pull request #11024 from ziggie1984/invoices-update-validation

Public commit record

What the developer wrote

Authored by ziggieXXX

58/100 · Thin
Merge pull request #11024 from ziggie1984/invoices-update-validation

invoices: refine update handling
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit tightens how LND processes invoice payments, especially for newer multi-path (MPP) and AMP invoices, keysend payments, and replayed payments. It adds checks that ensure the right payment preimage is used for each invoice type and that AMP invoices cannot be processed through the older legacy path. The changes are defensive hardening rather than a single obvious exploit fix, but they close several paths where an attacker might trick LND into settling an invoice incorrectly or using the wrong secret.

Recommended action

Treat as a security-hardening fix and include in release notes. Users running routing nodes should upgrade when available, especially if they accept AMP, keysend, or MPP payments. Review related invoice logic for any remaining paths that assume preimage presence.

Security signals we found

01

Preimage validation added for AMP and regular invoice replays

02

AMP invoices forced into MPP update path, preventing legacy-path processing

03

Legacy settlement now fails when invoice-level preimage is missing

04

Keysend preimage now validated against payment hash instead of trusting custom record presence

05

New unit tests cover mismatch, missing preimage, and keysend preimage mismatch cases

Risk score

Why this scored 63/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 10/15
Affected reach 12/15
Confidence 7/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.