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

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

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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 available:** No
- **Published:** 21 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-6552-m3hr-mqwj

## 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 (Improperly Implemented Security Check for Standard)

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65058 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-65058 in the wild and no public exploit code.

Affected product: Trezor Safe 3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-65058/ (Markdown: https://insights.sbomify.com/CVE-2026-65058/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-65058
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-65058
- OSV: https://osv.dev/vulnerability/CVE-2026-65058

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-65058/
Summaries are generated and may contain mistakes; the official description above is the record.