Repository navigation
advisories: CLN crashes when two channels share a funding outpoint - #16
Merged
morehouse merged 1 commit intoNov 13, 2026
Conversation
morehouse
requested changes
Nov 9, 2026
|
|
||
| ## Timeline | ||
|
|
||
| - **2026-07-03:** Duplicate funding outpoint reported publicly as a spec violation in [issue #9274](https://github.com/ElementsProject/lightning/issues/9274). |
Member
There was a problem hiding this comment.
nit:
Suggested change
| - **2026-07-03:** Duplicate funding outpoint reported publicly as a spec violation in [issue #9274](https://github.com/ElementsProject/lightning/issues/9274). | |
| - **2026-07-02:** Duplicate funding outpoint reported publicly as a spec violation in [issue #9274](https://github.com/ElementsProject/lightning/issues/9274). |
Member
Author
There was a problem hiding this comment.
Yeah, it's because of our timezone difference. For me, it's still 2026-07-03, but I've updated it anyway
|
|
||
| ## Takeaways | ||
|
|
||
| - **Upgrade to Core Lightning v26.06.6 or later.** |
Member
There was a problem hiding this comment.
Shouldn't we suggest to upgrade to v26.06.8 or later. Since in the fix section is describing a possible attack at v26.06.6.
Suggested change
| - **Upgrade to Core Lightning v26.06.6 or later.** | |
| - **Upgrade to Core Lightning v26.06.8 or later.** |
There was a problem hiding this comment.
Upgrade and always ensure your Core Lightning node is running the latest available release, subsequent releases may contain important security fixes.
| On reconnect, CLN hands its connection daemon a subdaemon for each channel, but the daemon looks them up by `channel_id` and finds the first one both times, so the second trips an assertion that crashes the whole node. | ||
| The outpoint never has to exist on chain, so the attack is **free**, and the attacker can crash the node again by reconnecting after every restart. | ||
|
|
||
| Upgrade to [Core Lightning v26.06.6](https://github.com/ElementsProject/lightning/releases/tag/v26.06.6) or later. |
There was a problem hiding this comment.
Upgrade and always ensure your Core Lightning node is running the latest available release, subsequent releases may contain important security fixes.
NishantBansal2003
force-pushed
the
cln-duplicate-outpoint-reconnect-dos
branch
2 times, most recently
from
November 13, 2026 12:38
f05366a to
2a233a5
Compare
NishantBansal2003
changed the title
morehouse
reviewed
Nov 13, 2026
morehouse
left a comment
morehouse
left a comment
Contributor
There was a problem hiding this comment.
- I think we should shorten up the intro paragraph to focus on impact (see inline suggestions); we can get into the details in the later sections.
morehouse
approved these changes
Nov 13, 2026
Signed-off-by: Nishant Bansal <nishant.bansal.282003@gmail.com>
NishantBansal2003
force-pushed
the
cln-duplicate-outpoint-reconnect-dos
branch
from
November 13, 2026 20:18
20203f4 to
32675ba
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.