Trezor Safe 3/Trezor Safe 5/Trezor Safe 7 Ethereum Signing Confirmation sign_tx/sign_tx_eip1559 logic error

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.7$0-$5k0.64-

Summaryinfo

A vulnerability has been found in Trezor Safe 3, Trezor Safe 5 and Trezor Safe 7 and classified as problematic. This affects the function sign_tx/sign_tx_eip1559 of the component Ethereum Signing Confirmation. Performing a manipulation results in logic error. This vulnerability is known as CVE-2026-65058. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Trezor Safe 3, Trezor Safe 5 and Trezor Safe 7 (the affected version unknown). This affects the function sign_tx/sign_tx_eip1559 of the component Ethereum Signing Confirmation. The manipulation with an unknown input leads to a logic error vulnerability. CWE is classifying the issue as CWE-840. This is going to have an impact on integrity. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-65058 since 07/21/2026. The exploitability is told to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

Applying the patch 70c9b0c is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.8
VulDB Meta Temp Score: 2.7

VulDB Base Score: 2.8
VulDB Temp Score: 2.7
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Logic error
CWE: CWE-840
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Patch: 70c9b0c

Timelineinfo

07/21/2026 CVE reserved
07/22/2026 +1 days Advisory disclosed
07/22/2026 +0 days VulDB entry created
07/22/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: github.com
Status: Confirmed

CVE: CVE-2026-65058 (🔒)
GCVE (CVE): GCVE-0-2026-65058
GCVE (VulDB): GCVE-100-381405

Entryinfo

Created: 07/22/2026 02:43
Changes: 07/22/2026 02:43 (53)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!