Vulnerability in Ethereum sign_tx / sign_tx_eip1559 flow (CVE-2026-65058)
Summary
Vulnerability in Ethereum sign_tx / sign_tx_eip1559 flow (CVE-2026-65058). Data can be tampered with by attackers. Mitigation: upgrade to 70c9b0c or later.
Original description
The description as published by the source.
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: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-65058 has been found in Ethereum sign_tx / sign_tx_eip1559 flow.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: upgrade Ethereum sign_tx / sign_tx_eip1559 flow to 70c9b0c or later.
If unsure, ask your IT team or search "Ethereum sign_tx / sign_tx_eip1559 flow CVE-2026-65058" on the vendor's site.
CVE-2026-65058 (Ethereum sign_tx / sign_tx_eip1559 flow) — CWE-358 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Patched: 70c9b0c — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-358) exists in Ethereum sign_tx / sign_tx_eip1559 flow.
Check the vendor advisory for the affected versions of Ethereum sign_tx / sign_tx_eip1559 flow.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
Update to 70c9b0c.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Ethereum sign_tx / sign_tx_eip1559 flow を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Ethereum sign_tx / sign_tx_eip1559 flow to 70c9b0cステージング環境で 70c9b0c に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory nvd.nist.gov
- advisory raw.githubusercontent.com
- advisory cve.org
- advisory github.com
- patch github.com
- web github.com