Vulnerability record

CVE-2026-65058

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker snapshot: Aug 8, 2026.

What it is

Reported

Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum sign_tx / sign_tx_eip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata to a victim then supply a different tail that changes the signed transaction. Fixed in 70c9b0c. Source description excerpt; complete tracked detail loads below.

NVD published: Jul 22, 2026 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What is affected

Reported

Trezor — Safe 3. Product-level identification only; no affected-version conclusion is available from this field.

NVD published: Jul 22, 2026 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Urgency and basis

Reported

Track · 113.2

Tracker decision tier from the evidence detailed below · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Exploitation evidence

Not reported

Not reported by tracked sources.

What to do

Not reported

Not reported by tracked sources.

Tracker guidance inferred from the decision tier: No action now. Remediate within standard update timelines. Monitor for change.

Evidence detail

Loading the full tracker evidence record…