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

Merge branch 'merge-v9.26.5'

Public commit record

What the developer wrote

Authored by Marko Bencun

45/100 · Thin
Merge branch 'merge-v9.26.5'
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This firmware update fixes several security issues in the BitBox02 hardware wallet. The most important change is that when signing Bitcoin transactions, the device now verifies that the previous transaction output's script (the 'pubkey script') matches the keypath the wallet is being asked to sign with. This closes a gap where a malicious or buggy host app could ask the wallet to sign an input while claiming it belongs to a different address/key than it actually does. The update also hardens the U2F/FIDO workflow so that an attacker cannot swap or replay a different request while the user is still confirming one on screen, and it prevents Bluetooth pairing prompts from popping up on top of other wallet tasks. The changelog simply says 'Security improvements', so the vendor has not publicly detailed the exact vulnerabilities.

Recommended action

Treat this as a security update and recommend users upgrade to v9.26.5. If a security advisory is later published, cross-reference the exact CVEs and attack scenarios. Review whether the pubkey-script validation change needs to be flagged for downstream wallet software that streams prevtx data, because mismatches will now fail signing.

Security signals we found

01

Bitcoin signing now validates prevtx pubkey_script against derived script from keypath/script config

02

New unit test explicitly rejects keypath/script mismatch for silent payment inputs

03

U2F pending APDU is stored and compared to prevent request swapping during user confirmation

04

U2F workflow guard prevents spawning overlapping unlock/confirm workflows

05

BLE pairing prompt blocked when HWW workflow owns the screen

06

CHANGELOG labels the release with 'Security improvements' but gives no CVE or details

Risk score

Why this scored 70/100

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