CVE-2026-65058 Trezor Safe improper security check in on-device display

Medium 5.9 Published Updated

Attackers can trick users into signing malicious Ethereum transactions by exploiting a flaw in how the device displays and binds calldata chunks.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2026-65058?

CVE-2026-65058 is a medium-severity vulnerability in Trezor Safe 3, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

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.

Weakness: CWE-358

Which versions are affected by CVE-2026-65058?

How do I fix CVE-2026-65058?

No fix has been published for CVE-2026-65058 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-65058 being exploited?

There is no known exploitation of CVE-2026-65058 in the wild and no public exploit code.

Sources

Also known as GHSA-6552-m3hr-mqwj.

Is CVE-2026-65058 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free