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

psbt: reject trailing final witness data

Public commit record

What the developer wrote

Authored by Boris Nagaev

45/100 · Thin
psbt: reject trailing final witness data
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This change tightens how a Bitcoin PSBT library extracts final witness data when turning a partially-signed transaction into a finished transaction. Previously, extra bytes after the declared witness stack were silently ignored. Now the library rejects such packets. That prevents malformed or crafted PSBTs from sneaking hidden data into the witness field, which could in some scenarios alter transaction behavior or be used to confuse downstream tools.

Recommended action

Review whether assertFullyConsumed is also needed on other deserialized PSBT fields (e.g., final scriptsig, taproot fields) and add regression tests with trailing-byte PSBTs. Consider a security advisory if malformed PSBTs could have caused incorrect extracted transactions in deployed wallets or services.

Security signals we found

01

strict parsing of serialized witness data

02

rejection of trailing bytes in PSBT final script witness

03

potential malleability / ambiguity reduction in PSBT extraction

Risk score

Why this scored 58/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 8/15
Affected reach 10/15
Confidence 7/10
Evidence quality 3/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.