Skip to content
Crypto.world

The Ledger

Electrum 4.8.3 Patches Bitcoin Wallet Transaction-Spoofing Flaw

Electrum released version 4.8.3 on October 24 after disclosing a high-severity flaw that let malicious servers replace a wallet’s unconfirmed transaction in its history. The fix checks signatures on the wallet’s own inputs, and Electrum says users of earlier versions should upgrade.

Electrum 4.8.3 Patches Bitcoin Wallet Transaction-Spoofing Flaw

A fake pending payment could replace the real one

Electrum disclosed a high-severity flaw in its Bitcoin wallet on October 24, 2026, and released version 4.8.3 to fix it. A malicious Electrum server could hide a transaction after a user broadcast it, then insert a conflicting, invalid transaction into the wallet’s history. If the user tried to speed up that fake payment with Replace-by-Fee (RBF), Electrum could sign it with a higher fee, sending funds to the attacker’s address.

The project says the issue affected versions before 4.8.3. It also reports two user disclosures: one person noticed a different transaction in the wallet history, while another lost money after bumping the fee on the substituted transaction. Electrum says some servers are carrying out the attack in the wild.

“Users should upgrade (and regularly do so in any case).”

SomberNight, Electrum security advisory

Why Electrum’s light-client design mattered

Electrum’s advisory explains that the client trusts its main server for unconfirmed, or mempool, transactions. In the described attack, the server withheld the user’s broadcast transaction and supplied a conflicting version whose outputs pointed to the attacker. The substituted transaction had invalid signatures, but earlier clients did not check those signatures on unconfirmed transactions before showing the payment in wallet history.

The advisory says the attacker’s output address in the reported cases shared the final four characters of the legitimate address, making the substitution harder to spot at a glance. In the loss reported to Electrum, the fake transaction carried a zero fee, apparently to encourage the user to raise it. Electrum rates the issue High and identifies it as GHSA-6jp4-8v48-cc5v.

Version 4.8.3 checks wallet-owned inputs

The patch makes Electrum verify signatures for inputs that belong to the user’s wallet before adding unconfirmed transactions to local history. Electrum says the change is included in version 4.8.3, which its release notes date to October 23; its official download server lists the 4.8.3 directory as added on October 24. The advisory lists versions below 4.8.3 as affected and 4.8.3 as patched.

The check has a stated limit: it covers inputs the wallet owns, not incoming transactions. Electrum says the light client lacks a full consensus engine and script interpreter, and validating other inputs would require recursively checking their unconfirmed parent transactions. Users who connect only to a server they trust, such as one they run themselves, are not affected according to the advisory.

Check every output if you cannot update

Electrum’s advisory recommends upgrading and gives a workaround for users who cannot do so immediately: check the destination addresses and amounts before signing any transaction, including a fee bump. That check matters because the attack relies on the wallet presenting the server’s substituted transaction as an ordinary pending payment.

Electrum’s 4.8.3 release notes also list other security fixes and wallet changes, including stricter plugin validation, changes to transaction signing, and additional checks for Lightning payments. The official download server lists the 4.8.3 release files; Electrum’s advisory identifies that version as the fix for the transaction-substitution vulnerability.

Sources

  1. Original source Electrum on GitHub · page 1 github.com

Other pages read

  1. Electrum on GitHub · Release NOTES github.com
  2. Electrum official download server download.electrum.org

Related stories

Explore

More articles