BitcoinBTC, coin
DevelopingSecurity

Core Lightning patches channel-close flaw that could skip the cheating penalty

CryptoSlate reports Core Lightning fixed a channel-close flaw in v26.06.7 that could let a peer broadcast a revoked channel state without triggering the cheating penalty.

Why it matters

The patch changes the penalty path that Lightning nodes rely on when a counterparty broadcasts a stale commitment, so operators on builds older than v26.06.7 are the ones affected. CryptoSlate gave no figures for funds at risk or lost, and the story has no stated effect on prices, market structure or regulation.

Key facts

Core Lightning fixed a channel-close flaw in release v26.06.7.

Reported by CryptoSlate

The flaw could let a peer broadcast an old, revoked channel state without triggering the penalty for cheating.

Reported by CryptoSlate

Before the fix, Core Lightning could treat a funding spend as a cooperative close when its outputs matched shutdown scripts already on record.

Reported by CryptoSlate

The flaw applied to a channel opened without an upfront shutdown script, where the peer could name its revoked commitment's output script in a shutdown message and then broadcast the old commitment.

Reported by CryptoSlate

The repair checks a transaction's locktime and sequence encoding to recognise a commitment before examining its outputs as a possible mutual close.

Reported by CryptoSlate

Bitcoin Optech published a Sept. 25 explanation of the now-public patch.

Reported by CryptoSlate

What happened

CryptoSlate reported that Core Lightning, a Lightning Network node implementation, patched a channel-close flaw in release v26.06.7. According to the outlet, the bug meant a peer could broadcast an old, revoked channel state without triggering the penalty that normally applies to such a move. CryptoSlate said the flaw depended on a specific channel setup: a peer that opened a channel without specifying an upfront shutdown script could name the output script of its revoked commitment in a shutdown message, then abandon the cooperative close and broadcast the old commitment, and matching outputs alone made the transaction look like a legitimate mutual close. The repair checks a transaction's locktime and sequence encoding to recognise a commitment before treating its outputs as a possible mutual close. CryptoSlate pointed to a Bitcoin Optech explanation dated Sept. 25 of the now-public patch, said the risk applies to operators still running older builds, and advised an upgrade plus a digest check for affected Docker images. Only CryptoSlate has reported the flaw, and the outlet's account describes a risk to operators rather than a reported loss of funds.

How the story developed

  1. First report

    First report by CryptoSlate

    Core Lightning patches flaw that could let revoked channel state escape penalty

    CryptoSlate

  2. Official statement

    Core Lightning publishes the fix in v26.06.7

    The patch notes and a regression test describe the change to the close and penalty logic.

    CryptoSlate

  3. Update

    Bitcoin Optech explains the patch

    Bitcoin Optech's Sept. 25 write-up describes the risk for operators still running older builds.

    CryptoSlate

  4. Update

    CryptoSlate reports the flaw and the fix

    The outlet lays out how a peer could evade the cheating penalty and what operators should do.

    CryptoSlate

Affected entities

Original sources

PublisherReportRolePublished
CryptoSlate
Crypto media
Core Lightning patches flaw that could let revoked channel state escape penaltyOriginal