Ledger fixed a signing flaw in its Ethereum app with version 1.22.2. The flaw let a connected dApp with the right access send commands during the review window and swap the transaction data the device signed, while the screen could keep showing the original details. Ledger and an outside security firm, TestMachine, disagree about who found it first and how disclosure was handled. Neither source reports confirmed losses.
| Item | Detail |
|---|---|
| Fixed in | Ledger Ethereum app 1.22.2 |
| Release date | August 12, 2026 per the changelog (GitHub shows a signed tag on August 13) |
| Confirmed on | Ledger Flex (public physical validation by TestMachine) |
| Possibly shared | Nano X, Nano S Plus, Stax and Apex, per TestMachine |
| Losses | None confirmed as of late August 2026 |
| CVE | None in the coverage |
How the flaw worked
CryptoSlate and Crowdfund Insider describe a race condition in certain clear-signing flows. A malicious dApp with WebHID access could send a second signing command that replaced the transaction in memory without a new review. A user could approve what looked like a small transfer while the device signed something else, such as an unlimited token approval to an attacker’s address. A second, related weakness let approval callbacks sign without checking that the app was still in the expected state.
Version 1.22.2 refuses a new signing session while a review is active and rejects an approval callback when the state no longer matches. Crowdfund Insider reports that private keys were not at risk of extraction. The danger was signing data that differed from what the screen showed. The bug lived in the Ethereum app on the device, so updating the phone or desktop software alone doesn’t replace it. Ledger advises updating through Ledger Live and keeping firmware current.
Who Benefits and How
- Anyone who signs Ethereum transactions on a Ledger gets the fix by updating the Ethereum app to 1.22.2 or later in Ledger Live.
- Read the details on your device screen for every approval, especially token approvals.
- Connect only to dApps you trust.
- This is general safety information, not investment advice.
A disputed story
Who found it first is disputed. Ledger CTO Charles Guillemet says Ledger’s Donjon team found it before TestMachine contacted Ledger’s bounty program, while TestMachine says its Azimuth scanner found it and that it shared the finding with Ledger. The timeline is contested too: TestMachine said on August 22 that the fix was not yet released, and Guillemet said on August 23 that it had shipped about two weeks earlier. The AI angle is also claimed by both sides. Ledger says Donjon used AI-assisted tools, TestMachine says its autonomous scanner found the same issue, and we can’t verify either claim. TestMachine validated the issue publicly on the Flex only and argues shared code extends it to the other current models. The Ethereum app manifest lists those models as build targets, but public physical validation covers only the Flex (CryptoSlate). Ledger hasn’t published a model-by-model statement in the sources we reviewed. Both outlets report no confirmed in-the-wild exploitation, lost funds or private-key extraction, which is an absence of reports, not an audit. The 1.22.2 changelog described the security change only in general terms, with no detailed advisory at release.
Quick answers
Which version fixes the Ledger signing flaw? Ethereum app 1.22.2.
Was anyone’s crypto stolen? No confirmed losses had been reported as of late August 2026, according to CryptoSlate and Crowdfund Insider.
Which Ledger models are affected? Public testing covers the Flex. TestMachine says the other current models share the code.
Sources
- CryptoSlate: Ledger patched an Ethereum app bug that could show one transaction and sign another (accessed Oct 13, 2026)
- Crowdfund Insider: Crypto Hardware Wallet Firm Ledger Addresses Ethereum App Signing Flaw Amid Disclosure Dispute (Aug 2026)
