LL
← All projectsLightning Labs

LND

Go implementation of a complete Lightning Network node.

BitcoinLightning NetworkNormal
Repository coverage

1687 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

186security candidates236second-pass queue1372AI analyses
162commits · 30 days
278commits · 60 days
643commits · 180 days
1422commits · 365 days
Backfill bands
Aug 5 → Feb 6405 seen5 candidatesComplete
Feb 6 → Jun 6665 seen28 candidatesComplete
Jun 6 → Jul 689 seen4 candidatesComplete
Jul 6 → Aug 569 seen0 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
387Strong · 80–100
837Adequate · 60–79
432Thin · 40–59
31Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Olaoluwa Osuntokun29659235474
ziggie49922422265
Elle Mouton26832268167
Yong60926172
ziggieXXX50617170
George Tsagkarelis37335167
LNBiG111173
Jared Tobin909171
yyforyongyu1211574070
bitromortac731154071
Erick Cestari26726070
Suheb746074
Analysis record

Published AI watches

Last scanned 43 minutes ago

Low 43 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11588 from ziggie1984/lnwallet/fix-reorg-wallet-sync-flake

This change fixes a wallet synchronization check in LND. Previously, the wallet only compared block heights to decide if it was fully caught up with the Bitcoin chain. During a chain reorganization (a temporary fork where one block is repl…

State synchronization check previously used height only, which is insufficient across reorgsFix adds block hash comparison to prevent false-positive sync statusCould cause LND to proceed while wallet state reflects an invalidated or not-yet-updated chain tip
8cdbf85cby Yong+224−1354 files
Vendor flagged security relevance
Moderate 51 AI analysisMessage 68 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #10708 from jtobin/alias-perms

This commit fixes a missing permission check on a new Lightning routing RPC called XFindBaseLocalChanAlias. Without the entry, any valid macaroon could call that RPC, bypassing the normal access-control list. The patch adds the required pe…

Missing macaroon authorization entry for an RPC endpointPotential privilege escalation: any valid macaroon could invoke an unprotected RPCRegression test added to enforce macPermissions coverage
98dc2b44by Olaoluwa Osuntokun+35−02 files
No security note in commit
Moderate 68 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11555 from yyforyongyu/invoice-settlement-public

This large LND patch changes when an ordinary invoice is considered 'paid'. Previously, releasing the preimage (the secret that lets the payer claim the funds) immediately marked the invoice as settled. Now the invoice enters a new interme…

New intermediate invoice/HTLC state prevents premature settlement reportingOn-chain HTLC outcomes persisted without opt-in to support restart recoveryForwarding package marker persisted before preimage release to avoid replay rejection on restart
895118acby Olaoluwa Osuntokun+4536−32048 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 80 · Strong
LL Lightning LabsLND BitcoinLightning Network

docs: describe invoice collection finality

This commit only adds documentation to the release notes. It describes a previously merged code change (PR 11555) about how LND handles invoice finality, but the commit itself contains no code, bug fixes, or behavior changes. There is noth…

9649d9f6by yyforyongyu+87−01 file
No security note in commit
Moderate 64 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11551 from ziggie1984/public-pr149-sanitized

This change fixes a bug in LND's invoice handling for multi-part payments (MPP and AMP). When a payment is split into several pieces (HTLCs), each piece is accepted individually. Previously, an old accepted piece could become too close to …

Fixes missing revalidation of accepted HTLC CLTV expiries at MPP/AMP set completionPrevents settlement of shards whose on-chain claim window has become unsafe while heldAdds new fail resolution ResultHtlcSetExpiryTooSoon and cancels the entire affected set
4b7447bcby Yong+281−347 files
Vendor flagged security relevance
Low 35 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11396 from yyforyongyu/task-lease-policy

This commit changes how LND's wallet locks (leases) unspent coins through its RPC interface. It removes a recently added 'release after N confirmations' option and replaces it with an explicit 'no expiry' flag. Old clients that still send …

Breaking API change that reserves removed protobuf fields to prevent accidental reintroductionExplicit rejection of legacy `release_after_spend_confs` parameters from old clients instead of silent fallbackValidation prevents conflicting no-expiry + duration lease settings before wallet state is touched
03e28a96by Yong+663−4029 files
Vendor flagged security relevance
Low 40 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11175 from ViktorT-11/2026-08-gossip-version-agnostic-store

This commit refactors how the Lightning Network Daemon (LND) stores and queries channel graph data so that the same channel or node can exist under both old (v1) and new (v2) gossip protocols without the database returning stale, missing, …

Cross-version data consistency: prevents a v2 channel shell from shadowing a usable v1 channel, which could affect routing decisions and RPC output.Cache consistency: ensures the in-memory pathfinding cache and the SQL-backed RPC reads agree on which channel version and policies are active.Bug fix: zombie edge info now carries the correct channel ID instead of 0, which could have caused incorrect channel identification during resurrection.
8c251687by Yong+3752−28726 files
No security note in commit
Moderate 61 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11440 from Roasbeef/fix-longstanding-correctness-bugs

This is a large bug-fix patch for LND (a Bitcoin Lightning Network node) that tightens correctness rules across many subsystems. It prevents several ways a node could mis-handle channel data, accept bad network gossip, commit corrupted dat…

Database transaction commit now aborts on read errors (etcd) - prevents silent data corruption / inconsistent stateGossip zombie marking removed for invalid funding script - prevents denial-of-service / channel graph poisoningWire message length bounding added to watchtower protocol - prevents memory exhaustion / malformed message parsing
0123a548by Olaoluwa Osuntokun+1424−11938 files
Vendor flagged security relevance
Moderate 59 AI analysisMessage 80 · Strong
LL Lightning LabsLND BitcoinLightning Network

invoices: require complete payment collection

This commit changes how LND handles multi-part Lightning payments when one part fails after the preimage was already released. Previously, the invoice could be marked as fully paid even if one shard was later reclaimed by the payer on-chai…

Changes invoice settlement semantics for released-but-failed HTLCsAdds new persisted HTLC state `HtlcStateFailed`Prevents invoice from reaching `ContractSettled` when any released shard fails
699ea930by Olaoluwa Osuntokun+492−4910 files
No security note in commit
Moderate 60 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

lnwallet: reject a zero CSV delay

This change tightens the rules for opening Lightning payment channels by refusing a setting called the CSV delay when it is set to zero. The CSV delay is the waiting period a user must endure before reclaiming their own funds from a channe…

Rejects a zero CSV delay that would eliminate the breach-remedy windowCentralizes the check in VerifyConstraints so all channel types and directions are coveredAdds explicit error type and unit test for the new constraint
266eba7bby Olaoluwa Osuntokun+81−03 files
Vendor flagged security relevance
Moderate 58 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

lnwallet+chanstate: keep persisted HTLC data readable

This commit fixes two bugs in how Lightning Network channel data is saved to disk. First, it stops extra 'aux' signatures meant only for advanced taproot channels from being saved on ordinary channels, where they don't belong. Second, it p…

Persisted state could become unreadable due to writer/reader size mismatchAuxiliary signatures for taproot overlay channels were persisted on plain channel HTLCsFix adds explicit serialization bound to prevent unreadable channel records
43c74723by Olaoluwa Osuntokun+101−25 files
No security note in commit
Low 39 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11374 from bitromortac/20261016-c7e5-dispatch

This commit adds the first end-to-end BOLT 12 'Offers' flow to LND: a new dev-only RPC and CLI command to create offers, plus a dispatcher that listens for incoming onion-message invoice requests and replies with signed BOLT 12 invoices. I…

New network-facing dispatcher answers invoice requests from any peer; rate and concurrency limits are appliedBlinded-path PathID check prevents reply linking to self-created paths, but TODO notes the check should move once offers can have offer_pathsCreateOffer RPC is restricted to dev builds and requires offchain:write macaroon permission
a9d4ca3bby bitromortac+3113−7838 files
No security note in commit
Moderate 60 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

invoices: reject settled AMP set shards

This change fixes a bug in LND's invoice handling for AMP (Atomic Multi-Path) payments. Previously, if someone tried to pay a fresh shard for an AMP set that was already fully paid, the invoice updater could return an internal error that w…

Denial-of-service vector: an internal updater error could force-fail a shared channel link, disrupting unrelated sibling HTLCsAMP invoice state machine edge case: reusable invoice stays open for other sets but must reject new shards for already-settled setsClean failure path introduced: ResultInvoiceNotOpen instead of error-driven link failure
99e3da37by yyforyongyu+49−02 files
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11282 from lightningnetwork/elle-base-branch-payment-service

This is a large feature merge for LND that adds a new optional RPC subsystem called switchrpc. It lets an external program hand a pre-built onion packet to LND for direct dispatch over a Lightning channel, instead of LND doing its own path…

New optional RPC surface (switchrpc) that accepts externally crafted onion packets and directly dispatches HTLCsIdempotency/deduplication added via InitAttempt durable write-ahead log and ErrPaymentIDAlreadyExistsStartup orphan cleanup fails half-open or pre-commit attempts to avoid hangs
11f79be0by Olaoluwa Osuntokun+11385−22458 files
Vendor flagged security relevance
Low 44 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11472 from yyforyongyu/task-sweep-rejections

This commit fixes a bug in LND's transaction sweeping logic. Previously, if the Bitcoin backend rejected a sweep transaction for a temporary or unknown reason (for example, the mempool was full, a network error occurred, or the rejection r…

Funds-availability / liveness fix: temporary or unknown mempool rejections could leave sweep inputs unspent.Error-handling reclassification: previously fatal errors now retryable.Retry metadata preservation: next fee rate and fee cap kept across attempts.
c5863e55by Yong+290−9720 files
No security note in commit
Low 32 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11292 from ViktorT-11/2026-10-harden-remote-signing-no-op

This change is a hardening fix for LND's remote-signing feature. Previously, if a node was configured to act as an outbound remote signer but was compiled without the required 'signrpc' and 'walletrpc' sub-servers, it would silently fall b…

silent-degradation-to-no-op preventedconfiguration-misconfiguration now surfaces as fatal errorbuild-tag-dependency explicitly validated at runtime
0c538e1fby Suheb+241−125 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

invoices: fix test whitespace

This commit only fixes blank-line spacing in a single test file to satisfy lint checks. It adds one blank line after a function signature and removes one trailing blank line. There are no code behavior changes, no bug fixes, and no securit…

a67d07f4by yyforyongyu+1−11 file
No security note in commit
Low 31 AI analysisMessage 92 · Strong
LL Lightning LabsLND BitcoinLightning Network

build: pin the new lint job actions by commit

This change updates two GitHub Actions used in the project's automated lint workflow so they are locked to specific commit hashes instead of floating version tags. A floating tag could be silently repointed to a different, possibly malicio…

CI/CD supply-chain hardeningthird-party action pinning by commit hashprevention of tag-movement attacks
2a9f137dby Olaoluwa Osuntokun+4−21 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 92 · Strong
LL Lightning LabsLND BitcoinLightning Network

build: fix the custom linter cache wiring for CI

This commit fixes the GitHub Actions CI setup for running a custom code linter. It makes sure Docker can read and write build caches correctly and that the built linter image is available for later steps. There is no user-facing security f…

6f665663by Olaoluwa Osuntokun+30−82 files
No security note in commit
Moderate 66 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11482 from Roasbeef/pub/unsigned-acked-wrap

This patch fixes a database bug in the Lightning Network Daemon (LND) where very long lists of unsigned, acknowledged channel updates could be silently truncated when saved to disk. Because the storage format used a 16-bit counter, lists l…

Integer truncation / wrap-around in serialization format (uint16 count)Silent data loss on restart due to undersized length fieldDefensive deserialization with count-modulo validation
7431093fby Olaoluwa Osuntokun+218−127 files
Vendor flagged security relevance
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidateactor: never park sends made from inside a receive turnby Olaoluwa Osuntokun · db6106a3 · Oct 28, 2026 · 4 filesMessage 90 · StrongModerate 53Details
Commit message · Olaoluwa Osuntokun

actor: never park sends made from inside a receive turn

In this commit, we make a send issued from an actor's own receive turn
non-blocking. Parking an actor on a full mailbox stalls its whole
mailbox, and a cycle of actors that do so deadlocks.

The actor loop now stamps the context handed to the behavior with a
turn marker, which is cleared when the turn returns. A Tell or Ask made
with such a context goes through a new in-turn path on the default
ChannelMailbox: it uses the channel when there is room and nothing is
queued ahead of it, and otherwise spills into a bounded overflow queue
that the receive loop refills the channel from, oldest first.

The queue is capped at ActorConfig.MailboxOverflowLimit, defaulting to
DefaultMailboxOverflowLimit. A send at the cap fails with
ErrMailboxOverflow, which an Ask surfaces on its Future. Tell can't
return an error, so it logs the drop. A context that outlives its turn,
in a goroutine the behavior spawned, parks like any other producer.
WithoutTurn clears the marker explicitly.

Delivery order is acceptance order. TrySend reports full while the
overflow is non-empty, and an ordinary blocking Send from outside the
actor first waits for the overflow to drain instead of writing to the
channel ahead of it. An owner can therefore enqueue a shutdown or
barrier message and know it runs after everything already accepted.
Drain yields the overflow after the channel.

The Mailbox interface is unchanged: the in-turn path is an optional
interface that ChannelMailbox implements.

This is ported from the in-turn send design in wavelength's
baselib/actor, with the Send ordering added.

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
memory safety
AI analysis · Moderate 53/100

This commit fixes a design flaw in LND's internal actor framework where an actor could freeze itself by sending a message to another actor whose mailbox was full. If several actors did this in a circle, the whole group could deadlock. The fix marks messages sent during an actor's own processing turn as 'in-turn' and routes them through a special non-blocking overflow queue, so the actor never stops moving. It also preserves message order and adds a hard cap so runaway message floods fail loudly instead of consuming unlimited memory.

Security candidatezpay32: resync BOLT 11 vectors with bolts#1368by Olaoluwa Osuntokun · 8f72c8f0 · Oct 27, 2026 · 2 filesMessage 81 · StrongInformational 20Details
Commit message · Olaoluwa Osuntokun

zpay32: resync BOLT 11 vectors with bolts#1368

In this commit, we pick up the corrected high-S vector from
lightning/bolts#1368, which drops the duplicate `s` field it used to
carry. The vector now reaches the signature check, so we expect
`ErrHighSSignature` for it rather than `ErrDuplicatePaymentAddr`.

81/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Informational 20/100

This commit updates LND's test data and test expectations to match a corrected official BOLT 11 specification test vector. The invoice string used to exercise 'high-S' signature rejection was changed so it no longer contains a duplicate 's' field. The test now expects the code to reject it specifically for the high-S signature, not for a duplicate field. It is a test-only alignment with the spec, not a functional code change.

Security candidatezpay32: assert why each fixed BOLT 11 vector is rejectedby Olaoluwa Osuntokun · 79c123b0 · Oct 27, 2026 · 3 filesMessage 100 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

zpay32: assert why each fixed BOLT 11 vector is rejected

In this commit, we make the tests show that each of the new decoder
rules is what rejects its invalid invoice, rather than any error.

The vector test only checked that an invalid vector failed, so a vector
rejected for the wrong reason still passed. That hid a real gap: the
spec's high-S vector also repeats its `s` field, so it's rejected as a
duplicate payment address before the signature is ever checked, and no
test exercised `ErrHighSSignature` at all.

We now map each vector this PR fixes to the sentinel error it must
produce, and add `TestDecodeHighSWithDestination`, which decodes the
same invoice (with a single `s` field) once with a high-S and once with
a low-S signature. A duplicate `s` case joins `TestParseTaggedFields`.
Dropping or breaking any of the three new checks now fails a test aimed
at it.

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Informational 15/100

This commit only improves and expands test code for the BOLT 11 invoice decoder. It makes existing tests verify the exact reason each invalid test invoice is rejected, and adds a new test specifically for high-S signature rejection. No production code is changed, so it cannot introduce or fix a runtime security vulnerability on its own.

Security candidatewalletrpc: reject retired lease requestsby yyforyongyu · e0269ab2 · Oct 22, 2026 · 2 filesMessage 68 · AdequateLow 48Details
Commit message · yyforyongyu

walletrpc: reject retired lease requests

Reject retired confirmation-count protobuf fields before lease
acquisition or PSBT funding so older clients cannot silently create
timed leases. Use preserved unknown fields and the existing protobuf
wire parser to keep the retired fields out of the public request schema.

Cover both public handlers with decoded old requests and stable error
identity assertions. Keep the existing wallet lifetime implementation.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 48/100

This change is a hardening patch, not an active exploit fix. LND removed two protobuf fields that let callers request timed output leases. Older clients still send those field numbers over the wire as 'unknown' protobuf data, so the server would silently ignore them and create a different kind of lease than the client expected. The patch now detects those retired field numbers in LeaseOutput and FundPsbt and returns an explicit error instead of silently falling through. The main risk is operational: an old client or script that relied on the removed fields will now fail fast rather than silently changing behavior.

Security candidatedocs: sync the v0.21.5 release notes with the release branchby ziggie · 6cbff7a7 · Oct 21, 2026 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · ziggie

docs: sync the v0.21.5 release notes with the release branch

The MuSig2 session cleanup and aux HTLC signature validation entries of
release-notes-0.21.5.md were in a different order on master than on
v0.21.x-branch. Use the release branch's order, so both documents are
identical.

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydocumentation-only discount
AI analysis · Informational 15/100

This commit only reorders two existing entries in the release notes document for version 0.21.5. No code, configuration, or behavior of the LND software is changed. It is a documentation-only edit to keep two copies of the release notes in the same order.

Security candidateMerge pull request #11380 from ziggie1984/fix-update-fee-floorby ziggieXXX · 732a9a0c · Oct 21, 2026 · 11 filesMessage 73 · AdequateModerate 59Details
Commit message · ziggieXXX

Merge pull request #11380 from ziggie1984/fix-update-fee-floor

lnwallet: reject fee updates below commit floor

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Moderate 59/100

This update to the Lightning Network Daemon (LND) fixes several related bugs around commitment transaction fee rates for anchor-style channels. It prevents LND from accepting or sending fee updates below the protocol minimum, clamps a configuration value that could overflow and silently turn into a much lower fee, and cleans up a wallet reservation leak when an incoming channel open is rejected. The practical effect is to stop channels from being created or updated with fees so low that they cannot carry payments, and to prevent a misconfiguration from accidentally disabling the intended fee cap.

Security candidateMerge pull request #11164 from ViktorT-11/2026-08-sync-gossip-with-specby Yong · 26b04676 · Oct 20, 2026 · 32 filesMessage 73 · AdequateLow 40Details
Commit message · Yong

Merge pull request #11164 from ViktorT-11/2026-08-sync-gossip-with-spec

lnwire: pull gossip v2 messages in line with BOLT taproot-gossip review updates

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathboot or update pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 40/100

This commit updates LND's experimental gossip-v2 protocol implementation to match a newer version of the Lightning BOLT specification. It changes how several peer-to-peer messages are encoded and decoded, adds stricter checks for required fields, and fixes edge cases such as default HTLC limits and address port handling. The changes are primarily a protocol conformance and hardening patch rather than a fix for a known active vulnerability.

Security candidateMerge pull request #11360 from saubyk/scripts/keys-removal-policyby Yong · 88a5b0ee · Oct 20, 2026 · 1 fileMessage 73 · AdequateInformational 20Details
Commit message · Yong

Merge pull request #11360 from saubyk/scripts/keys-removal-policy

scripts: document release signing key removal policy

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarydocumentation-only discountmerge-commit duplicate discount
AI analysis · Informational 20/100

This commit only adds documentation explaining when and why old release signing keys are removed from the project. It does not change any code, verification logic, or cryptographic handling. There is no security vulnerability in the commit itself.

Security candidateMerge pull request #11343 from saubyk/scripts/remove-ellemouton-keyby Yong · a1cc86d6 · Oct 19, 2026 · 6 filesMessage 73 · AdequateLow 29Details
Commit message · Yong

Merge pull request #11343 from saubyk/scripts/remove-ellemouton-key

scripts: remove expired and unused release signing keys

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarymerge-commit duplicate discount
AI analysis · Low 29/100

This commit removes several expired or unused PGP public keys from the LND release verification script. It does not change any application code, wallet logic, or network behavior. The main effect is that future release signature checks will no longer trust signatures made by the removed keys, which is a routine cleanup of release-signing trust material.

Security candidateMerge pull request #11307 from bitromortac/20261008-41a8-dispatchby ziggieXXX · cc6f08b8 · Oct 16, 2026 · 10 filesMessage 73 · AdequateLow 29Details
Commit message · ziggieXXX

Merge pull request #11307 from bitromortac/20261008-41a8-dispatch

bolt12handler: add BOLT 12 invoice generation and signing

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 29/100

This commit adds new code to LND that lets a node create and cryptographically sign BOLT 12 invoices. It also changes how invoice signing works so that signing can be done by a remote signer that never sees the node's private key. The change is a feature addition, not a fix for a known bug or vulnerability. There is no evidence in the commit message or diff that the project treats this as a security patch.

Security candidateMerge pull request #11311 from ziggie1984/fix-sql-graph-empty-signaturesby Olaoluwa Osuntokun · 4ea5f814 · Oct 12, 2026 · 4 filesMessage 73 · AdequateLow 30Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11311 from ziggie1984/fix-sql-graph-empty-signatures

graph/db: normalize empty policy signatures

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarymerge-commit duplicate discount
AI analysis · Low 30/100

This is a bug-fix patch for LND's native SQLite graph migration. When moving channel data from the older key-value (KV) database format to the new SQLite format, empty routing-policy signatures were stored differently: KV used an empty-but-non-nil byte slice, while SQLite returned nil. The migration validation treated these as unequal, causing the migration to fail. The fix normalizes empty signatures to nil before comparison so the migration succeeds. It is a correctness/reliability fix rather than an exploitable vulnerability.

Security candidategraph/db: normalize empty policy signaturesby ziggie · 4eec0af2 · Oct 9, 2026 · 2 filesMessage 45 · ThinInformational 24Details
Commit message · ziggie

graph/db: normalize empty policy signatures

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 24/100

This commit fixes a test-only data comparison mismatch during a database migration. When moving channel policy data to SQLite, empty signature fields were stored differently (nil vs empty slice), causing validation comparisons to fail. The fix normalizes empty signatures to nil before comparison, and adds a test case covering this scenario. It does not appear to affect live node behavior or introduce a security vulnerability.

Security candidateMerge pull request #11068 from GeorgeTsagk/auxsig-requiredby ziggieXXX · a8970c6e · Oct 9, 2026 · 5 filesMessage 73 · AdequateHigh 70Details
Commit message · ziggieXXX

Merge pull request #11068 from GeorgeTsagk/auxsig-required

lnwallet: reject commitments missing aux HTLC signatures

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · High 70/100

This commit fixes a security gap in LND's taproot overlay channels. Previously, a channel peer could send a commitment transaction with missing or mismatched auxiliary HTLC signatures, and LND would still accept it. Those signatures are needed to safely recover funds if the channel is later force-closed. Without them, HTLCs could be left on disk with empty signatures, making them unsweepable at force-close time and potentially locking up funds. The patch now rejects such commitments, causing a force close instead of silently accepting a dangerous state. It also fixes a test helper so that restarting a channel does not drop the auxiliary signer configuration.

Security candidateMerge pull request #11290 from allenpiscitello/fix/blinded-path-fee-overflowby ziggieXXX · d9a52264 · Oct 7, 2026 · 3 filesMessage 78 · AdequateModerate 56Details
Commit message · ziggieXXX

Merge pull request #11290 from allenpiscitello/fix/blinded-path-fee-overflow

blindedpath: avoid uint32 overflow in accumulated fee calc

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
memory safetymerge-commit duplicate discount
AI analysis · Moderate 56/100

This commit fixes a math overflow bug in LND's blinded payment paths. When building a private (blinded) route for an invoice, the node adds up per-hop fees using 32-bit unsigned integers. If the total base fee or fee rate exceeded about 4295, the sum would wrap around to a tiny number. The invoice would then advertise fees that were too low, so any payer sending through that path would underpay and the payment would fail. The fix uses checked 64-bit arithmetic and simply skips any route whose true fees don't fit in the invoice's 32-bit fields, rather than advertising incorrect fees.

Security candidatesqldb: prevent retry backoff overflowby ziggie · 34b0d4ef · Oct 1, 2026 · 4 filesMessage 50 · ThinLow 36Details
Commit message · ziggie

sqldb: prevent retry backoff overflow

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
memory safety
AI analysis · Low 36/100

This commit fixes a math overflow bug in the database retry logic of LND, a Bitcoin Lightning Network node. When retrying failed database operations, the code could calculate a wait time so large that it wrapped around to a negative number, potentially causing immediate retries, unexpected behavior, or node instability. The fix caps each step of the calculation and uses safer integer math. It is a defensive hardening change rather than a directly exploitable remote vulnerability.

Security candidateMerge pull request #11281 from ziggie1984/lint-intrange-cleanupby Olaoluwa Osuntokun · 95c56eeb · Sep 30, 2026 · 49 filesMessage 58 · ThinInformational 15Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11281 from ziggie1984/lint-intrange-cleanup

lnd: use Go integer ranges

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit is a large but purely cosmetic code cleanup. It replaces old-style Go for loops like 'for i := 0; i < N; i++' with the newer 'for i := range N' syntax introduced in Go 1.22. No logic, behavior, or security properties of the code are changed.

Security candidatebuild: read live PR labels in check-label actionby ziggie · 45c9cfff · Sep 24, 2026 · 2 filesMessage 92 · StrongInformational 21Details
Commit message · ziggie

build: read live PR labels in check-label action

The check-label composite action evaluated
github.event.pull_request.labels, which is a snapshot captured when the
pull_request event fired. A label such as no-changelog or no-itest added
after the run kicked off was therefore never seen, not even when
re-running the failed job, because a re-run reuses the original event
payload. The only workaround was pushing a new commit.

Query the current label set through the API instead and only fall back
to the event payload when there is no PR number (push and merge_group
runs) or the API call fails. Re-running a failed job now picks up labels
added after the run started.

The workflow declares explicit permissions, so grant pull-requests: read
for the API call.

92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
credential or privilege statedocumentation-only discount
AI analysis · Informational 21/100

This is a GitHub Actions workflow fix, not a vulnerability in the LND lightning node software itself. It changes how a CI check reads pull-request labels so that re-running a failed job sees labels added after the run started. The change adds a GitHub API call and grants the workflow read-only access to pull-request metadata. There is no direct security risk to LND users or funds.

Security candidateMerge pull request #11132 from yyforyongyu/task-11129-pongby Olaoluwa Osuntokun · d3d1f1d0 · Sep 22, 2026 · 5 filesMessage 58 · ThinModerate 53Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11132 from yyforyongyu/task-11129-pong

peer: answer every valid ping

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
authentication pathmerge-commit duplicate discount
AI analysis · Moderate 53/100

This change fixes how LND answers network 'ping' messages from other Lightning nodes. Previously, LND would sometimes silently ignore valid pings to limit reply traffic, which violates the Lightning protocol (BOLT 1) and could make a peer think the connection is dead. Now LND replies to every valid ping, while still disconnecting peers that flood too many pings. The cost of a reply is counted against a single flood budget based on how large the reply would be.

Security candidateMerge pull request #11198 from gijswijs/amp-setlocal-reconstruction-fixby Olaoluwa Osuntokun · 88959aec · Sep 19, 2026 · 4 filesMessage 73 · AdequateModerate 60Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11198 from gijswijs/amp-setlocal-reconstruction-fix

invoices: cancel only the failing AMP set on reconstruction failure

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Moderate 60/100

This change fixes a bug in LND's handling of AMP (Atomic Multi-Path) payments. Previously, if one partial payment set failed to reconstruct its secret preimage, the entire invoice was canceled, including unrelated partial payment sets from other payers. Now only the failing set is canceled, and the invoice stays open so other valid sets can still complete and settle. This is a correctness/availability fix for reusable AMP invoices.

Security candidatebuild: fix Go 1.27 compatibilityby ziggie · 6b54a387 · Sep 18, 2026 · 6 filesMessage 100 · StrongInformational 20Details
Commit message · ziggie

build: fix Go 1.27 compatibility

Upgrade the custom golangci-lint from v2.4.0 to v2.13.2 because the older
version reports false type-checking errors for generic mutex code when it
runs with Go 1.27. Refresh the tools module dependencies, account for the
renamed exhaustruct_v5 linter, and disable the deprecated gomodguard while
leaving gomodguard_v2 active.

Apply Go 1.27's gofmt output to the PSBT test's composite-literal return.

Lower the consecutive-SCID zlib test boundary from 30,794 to 30,792. Go
1.27 changed compress/flate output, making 30,793 SCIDs exceed the
65,535-byte Lightning message limit while 30,792 still fit.

100/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 20/100

This commit is a routine build-and-test maintenance patch to make the LND codebase compile and pass tests with the upcoming Go 1.27 release. It upgrades the project's custom linter tool, refreshes many indirect tool dependencies, adjusts one test's formatting, and lowers a test constant that checks how many compressed channel IDs fit in a Lightning message. There is no direct security fix here; it is a compatibility and test-hygiene change.

Security candidateinvoices: cancel only the failing AMP set on reconstruction failureby Gijs van Dam · d74ab6fa · Sep 16, 2026 · 2 filesMessage 83 · StrongModerate 60Details
Commit message · Gijs van Dam

invoices: cancel only the failing AMP set on reconstruction failure

When an AMP set completes but fails preimage reconstruction, updateMpp
issued a CancelInvoiceUpdate that canceled the greater invoice. For
reusable static AMP invoices this is too broad: the failure is a
set-local condition, since only the HTLCs of the failing set can never
settle. Other sets accepted on the same invoice are unaffected by the
failure and should remain payable.

Issue a CancelHTLCsUpdate scoped to the failing set instead, keeping
the invoice open. Adds a regression test verifying that a concurrently
accepted set on the same invoice survives a failing set and can still
settle.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidenceboot or update path
AI analysis · Moderate 60/100

This commit fixes a bug in LND's invoice handling for reusable AMP (Atomic Multi-Path) invoices. Previously, if one payment set failed to reconstruct its preimage, the entire invoice was canceled, even though other valid payment sets on the same invoice were unaffected. Now, only the failing set is canceled, and the invoice stays open so other payers can still complete their payments. This is a correctness and availability fix for a specific Lightning Network payment feature.

Security candidatebolt12: cover the amount overflow guardby bitromortac · 3c8e2bcb · Sep 10, 2026 · 1 fileMessage 91 · StrongModerate 60Details
Commit message · bitromortac

bolt12: cover the amount overflow guard

The request side had a test for the offer_amount times quantity overflow, the
invoice side did not, and it was the only uncovered branch in the invoice
amount check. Verified by neutering the guard, which makes the new case accept
an invoice_amount of one against an authorized amount that wrapped to zero.

Finding F9.
https://github.com/lightningnetwork/lnd/pull/10941#discussion_r3599755895

91/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
memory safety
AI analysis · Moderate 60/100

This commit adds a test to ensure that when a BOLT 12 invoice is validated against a request, the multiplication of the offer amount by the requested quantity cannot overflow and wrap around to zero. Without this guard, a malicious or malformed invoice could claim an authorized amount of zero and pass validation even though the real intended amount was huge. The actual overflow guard already exists in production code; this change only adds the missing test coverage.

Security candidateMerge pull request #11061 from bitromortac/2604-bolt12-1fby Yong · 1049d301 · Sep 8, 2026 · 15 filesMessage 73 · AdequateLow 34Details
Commit message · Yong

Merge pull request #11061 from bitromortac/2604-bolt12-1f

bolt12: add Merkle tree and BIP-340 message signatures

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 34/100

This commit adds the missing cryptographic signature layer for BOLT 12 offers in LND. It builds a Merkle tree from the message fields, signs that tree with a BIP-340 Schnorr signature, and now rejects invoice requests and invoices whose signatures do not verify. It also tightens decoding so non-minimal encodings of feature bits and amounts are rejected, preventing a message from being accepted in one form but re-encoded into a different byte form that would break the signature.

Security candidatebolt12: verify invoice_request and invoice signatures on readby bitromortac · aa8bd19f · Sep 2, 2026 · 3 filesMessage 88 · StrongModerate 60Details
Commit message · bitromortac

bolt12: verify invoice_request and invoice signatures on read

ValidateInvoiceRequestRead and ValidateInvoiceRead now run
VerifyInvoiceRequest and VerifyInvoice as their final step, so a
decoded message whose BIP-340 signature does not verify against
invreq_payer_id or invoice_node_id is rejected instead of only
checked for presence. This satisfies the reader-side MUSTs of the
BOLT 12 invoice_request and invoice requirements, and the docstrings
now state the contract instead of deferring it to callers.

The invoice_request wiring is pinned by the spec's signed vector; no
signed invoice vector exists, so the invoice side is pinned by
round-trip tests. Reader-validation fixtures now sign with Bob's
key, and the happy-path invoice_request test reuses the shared
validInvoiceRequest fixture.

88/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validation
AI analysis · Moderate 60/100

This change makes LND's BOLT 12 invoice and invoice-request reader actually check that the digital signature is valid, instead of only checking that a signature field exists. Before, an attacker could craft or modify a BOLT 12 message and include any 64-byte placeholder as a 'signature'; the reader would accept it as long as the field was present. Now the reader verifies the signature cryptographically against the claimed sender public key, rejecting forgeries and tampered messages. This is a security-hardening fix that closes a real authentication gap.

Security candidateMerge pull request #11090 from yyforyongyu/task-peer-managerby Yong · d24719e0 · Aug 28, 2026 · 15 filesMessage 73 · AdequateHigh 76Details
Commit message · Yong

Merge pull request #11090 from yyforyongyu/task-peer-manager

peer: bound peer-controlled resource growth

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update pathauthentication pathmerge-commit duplicate discount
AI analysis · High 76/100

This update to the LND Lightning node software fixes two security-related bugs. First, it prevents a connected peer from exhausting the node's memory or CPU by sending floods of ping messages or by forcing the node to queue too many outbound messages. Second, it fixes a signature mismatch in channel-update messages that carry inbound fees, so updates are signed exactly as they are broadcast and unknown extra data is preserved. The release notes explicitly describe both as preventing peer-controlled resource exhaustion and remote signature failures.