Bitcoin Core merges safeguard for PSBT signatures into development branch
One outlet reports Bitcoin Core merged a Sept. 25 fix for a PSBT flaw in which a valid signature can survive a changed recipient; wallet vendors must review their own signing logic.
Why it matters
The change sits in a development branch rather than a release, so wallet software that builds and signs PSBTs may need its own review of the missing-output case. The reporting does not say whether any funds were ever exposed or exploited.
Key facts
Bitcoin Core merged a safeguard against signing transactions that may not bind funds to the payment destination a user approved.
Reported by CryptoSlate
The change was merged into Bitcoin Core's master development branch on Sept. 25.
Reported by CryptoSlate
The change targets a narrow flaw in partially signed Bitcoin transactions that could produce a valid signature without protecting the intended output.
Reported by CryptoSlate
The issue does not expose a user's private key.
Reported by CryptoSlate
A signature can remain valid even when the transaction's recipient is changed under specific conditions.
Reported by CryptoSlate
The weakness involves a signing mode designed to commit an input to the output in the corresponding position, and protection breaks down differently depending on the type of bitcoin being spent when no output exists at that position.
Reported by CryptoSlate
For legacy inputs, the missing-output case can produce a signature over a fixed hash value, and Bitcoin Core developers said that signature may then be reusable against other unspent outputs controlled by the same key when the same structural conditions are present.
Reported by CryptoSlate
The fix is only in Bitcoin Core's development branch, leaving wallet providers to review their own signing logic.
Reported by CryptoSlate
What happened
One crypto news outlet reported that Bitcoin Core merged a safeguard, on Sept. 25, against signing transactions that may not bind funds to the payment destination a user approved, and that the change went into Bitcoin Core's master development branch. The report says the change targets a narrow flaw in partially signed Bitcoin transactions, or PSBTs, that could produce a valid signature without protecting the intended output, and that the issue does not expose a user's private key. The risk described is different: under specific conditions a signature can remain valid even when the transaction's recipient is changed. The weakness involves a signing mode designed to commit an input to the output in the corresponding position, and Bitcoin Core developers said a signature produced for legacy inputs in the missing-output case, over a fixed hash value, may then be reusable against other unspent outputs controlled by the same key when the same structural conditions are present. Bitcoin Optech highlighted the update on Oct. 2, and the outlet noted that the fix is only in the development branch, leaving wallet providers to review their own signing logic. No second outlet is on record for this, and the account of how the flaw behaves for SegWit v0 spends stops mid-sentence in the material available to the desk.
How the story developed
- First report
First report by CryptoSlate
Bitcoin Core’s new fix closes gap that could redirect funds without stealing keys
- Official statement
Bitcoin Core merges the PSBT signing safeguard into its master development branch
The merged change targets signatures that may not bind funds to the approved payment destination.
- Update
Bitcoin Optech highlights the update
Bitcoin Optech covered the Bitcoin Core change on Oct. 2.
- Update
Single crypto news outlet publishes the account of the flaw
The only report on record describes the missing-output case and quotes Bitcoin Core developers on signature reuse.
Affected entities
Original sources
| Publisher | Report | Role | Published |
|---|---|---|---|
| CryptoSlate Crypto media | Bitcoin Core’s new fix closes gap that could redirect funds without stealing keys | Original |