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

Harden PSBTv2 parsing

Public commit record

What the developer wrote

Authored by scgbckbone

28/100 · Opaque
Harden PSBTv2 parsing
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
The short version

What changed, and why it matters

This commit tightens how COLDCARD reads PSBTv2 (Partially Signed Bitcoin Transaction version 2) files. It now rejects several malformed or ambiguous encodings that could previously be accepted: extra key data attached to fields that should have none, badly encoded input/output counts, and PSBTv2 files that are missing the required global version field. These are defensive hardening fixes rather than a single obvious exploit, but they close paths where a malicious or malformed PSBT could confuse the wallet's transaction parser.

Recommended action

Treat as a security-relevant hardening patch. Users should upgrade to a firmware release containing this commit, and developers should review whether any other PSBTv2 fields are still missing singleton validation.

Security signals we found

01

PSBT parser hardening

02

rejection of non-canonical compact-size encodings

03

enforcement of singleton key-data emptiness

04

mandatory PSBTv2 global version field

05

defensive input validation

Risk score

Why this scored 59/100

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