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.
CVE-2026-65058
Score 5.3 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 20.1%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 21, 2026commit 70c9b0c07748 (trezor/trezor-firmware)
Fix landed in trezor/trezor-firmware commit 70c9b0c07748 — awaiting tagged release
https://github.com/trezor/trezor-firmware/commit/70c9b0c07748Vendor Advisories for CVE-2026-65058(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 22:58 UTCEG score recompute
- 2026-07-22 22:58 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 21:24 UTCEG score recompute
- 2026-07-21 20:45 UTCEG score recompute
- 2026-07-21 20:43 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-65058?
When was CVE-2026-65058 disclosed?
Is CVE-2026-65058 actively exploited?
What is the CVSS score of CVE-2026-65058?
How do I remediate CVE-2026-65058?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65058
Is Your Infrastructure Affected by CVE-2026-65058?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.