VA-26-202-02
Vulnerability from csaf_cisa - Published: 2026-07-21 14:39 - Updated: 2026-07-21 14:39Summary
Trezor Safe improper security check in on-device display
Notes
Legal Notice: All information products included in [https://github.com/cisagov/CSAF/tree/develop/csaf_files/IT/white](https://github.com/cisagov/CSAF/tree/develop/csaf_files/IT/white) are provided \"as is\" for informational purposes only. The Department of Homeland Security (DHS) does not provide any warranties of any kind regarding any information contained within. DHS does not endorse any commercial product or service, referenced in this product or otherwise. Further dissemination of this product is governed by the Traffic Light Protocol (TLP) marking in the header. For more information about TLP, see [https://us-cert.cisa.gov/tlp/](https://us-cert.cisa.gov/tlp/).
Countries and Areas Deployed: Worldwide
Critical Infrastructure Sectors: Information Technology
Risk Evaluation: 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.
Recommended Practices: Fixed in 70c9b0c.
Company Headquarters Location: United States
5.3 (Medium)
Affected products
Known affected
3 products
References
4 references
{
"document": {
"category": "csaf_vex",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE"
}
},
"lang": "en-US",
"notes": [
{
"category": "legal_disclaimer",
"text": "All information products included in [https://github.com/cisagov/CSAF/tree/develop/csaf_files/IT/white](https://github.com/cisagov/CSAF/tree/develop/csaf_files/IT/white) are provided \\\"as is\\\" for informational purposes only. The Department of Homeland Security (DHS) does not provide any warranties of any kind regarding any information contained within. DHS does not endorse any commercial product or service, referenced in this product or otherwise. Further dissemination of this product is governed by the Traffic Light Protocol (TLP) marking in the header. For more information about TLP, see [https://us-cert.cisa.gov/tlp/](https://us-cert.cisa.gov/tlp/).",
"title": "Legal Notice"
},
{
"category": "other",
"text": "Worldwide",
"title": "Countries and Areas Deployed"
},
{
"category": "other",
"text": "Information Technology",
"title": "Critical Infrastructure Sectors"
},
{
"category": "summary",
"text": "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.",
"title": "Risk Evaluation"
},
{
"category": "general",
"text": "Fixed in 70c9b0c.",
"title": "Recommended Practices"
},
{
"category": "other",
"text": "United States",
"title": "Company Headquarters Location"
}
],
"publisher": {
"category": "coordinator",
"contact_details": "https://www.cisa.gov/report",
"issuing_authority": "CISA",
"name": "CISA",
"namespace": "https://www.cisa.gov/"
},
"references": [
{
"category": "self",
"summary": "Vulnerability Advisory VA-26-202-02 CSAF",
"url": "https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-202-02.json"
}
],
"title": "Trezor Safe improper security check in on-device display",
"tracking": {
"current_release_date": "2026-07-21T14:39:13Z",
"generator": {
"engine": {
"name": "VINCE-NT",
"version": "1.15.0+build.101"
}
},
"id": "VA-26-202-02",
"initial_release_date": "2026-07-21T14:39:13Z",
"revision_history": [
{
"date": "2026-07-21T14:39:13Z",
"number": "1.0.0",
"summary": "Initial publication"
}
],
"status": "final",
"version": "1.0.0"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c70c9b0c",
"product": {
"name": "Trezor Safe 3 \u003c70c9b0c",
"product_id": "CSAFPID-0001"
}
},
{
"category": "product_version",
"name": "70c9b0c",
"product": {
"name": "Trezor Safe 3 70c9b0c",
"product_id": "CSAFPID-0002"
}
}
],
"category": "product_name",
"name": "Safe 3"
},
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c70c9b0c",
"product": {
"name": "Trezor Safe 5 \u003c70c9b0c",
"product_id": "CSAFPID-0003"
}
},
{
"category": "product_version",
"name": "70c9b0c",
"product": {
"name": "Trezor Safe 5 70c9b0c",
"product_id": "CSAFPID-0004"
}
}
],
"category": "product_name",
"name": "Safe 5"
},
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c70c9b0c",
"product": {
"name": "Trezor Safe 7 \u003c70c9b0c",
"product_id": "CSAFPID-0005"
}
},
{
"category": "product_version",
"name": "70c9b0c",
"product": {
"name": "Trezor Safe 7 70c9b0c",
"product_id": "CSAFPID-0006"
}
}
],
"category": "product_name",
"name": "Safe 7"
}
],
"category": "vendor",
"name": "Trezor"
}
]
},
"vulnerabilities": [
{
"acknowledgments": [
{
"names": [
" Oleh Konko"
],
"organization": "1seal"
}
],
"cve": "CVE-2026-65058",
"cwe": {
"id": "CWE-358",
"name": "Improperly Implemented Security Check for Standard"
},
"notes": [
{
"category": "summary",
"text": "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.",
"title": "Description"
},
{
"category": "details",
"text": "SSVCv2/E:N/A:N/T:P/2026-06-30T18:42:58Z/",
"title": "SSVC"
}
],
"product_status": {
"fixed": [
"CSAFPID-0002",
"CSAFPID-0006",
"CSAFPID-0004"
],
"known_affected": [
"CSAFPID-0001",
"CSAFPID-0005",
"CSAFPID-0003"
]
},
"references": [
{
"category": "external",
"summary": "github.com",
"url": "https://github.com/trezor/trezor-firmware/commit/70c9b0c07748"
},
{
"category": "external",
"summary": "CVE-2026-65058",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65058"
},
{
"category": "external",
"summary": "VA-26-202-02 CSAF",
"url": "https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-202-02.json"
}
],
"release_date": "2026-03-19T00:00:00Z",
"remediations": [
{
"category": "vendor_fix",
"date": "2026-03-19T00:00:00Z",
"details": "Fixed in 70c9b0c.",
"product_ids": [
"CSAFPID-0001"
],
"url": "https://github.com/trezor/trezor-firmware/commit/70c9b0c07748"
},
{
"category": "vendor_fix",
"date": "2026-03-19T00:00:00Z",
"details": "Fixed in 70c9b0c.",
"product_ids": [
"CSAFPID-0002"
],
"url": "https://github.com/trezor/trezor-firmware/commit/70c9b0c07748"
},
{
"category": "vendor_fix",
"date": "2026-03-19T00:00:00Z",
"details": "Fixed in 70c9b0c.",
"product_ids": [
"CSAFPID-0005"
],
"url": "https://github.com/trezor/trezor-firmware/commit/70c9b0c07748"
},
{
"category": "vendor_fix",
"date": "2026-03-19T00:00:00Z",
"details": "Fixed in 70c9b0c.",
"product_ids": [
"CSAFPID-0006"
],
"url": "https://github.com/trezor/trezor-firmware/commit/70c9b0c07748"
},
{
"category": "vendor_fix",
"date": "2026-03-19T00:00:00Z",
"details": "Fixed in 70c9b0c.",
"product_ids": [
"CSAFPID-0003"
],
"url": "https://github.com/trezor/trezor-firmware/commit/70c9b0c07748"
},
{
"category": "vendor_fix",
"date": "2026-03-19T00:00:00Z",
"details": "Fixed in 70c9b0c.",
"product_ids": [
"CSAFPID-0004"
],
"url": "https://github.com/trezor/trezor-firmware/commit/70c9b0c07748"
}
],
"scores": [
{
"cvss_v3": {
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"products": [
"CSAFPID-0001",
"CSAFPID-0005",
"CSAFPID-0003"
]
}
],
"title": "Trezor Safe improper security check in on-device display"
}
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…