Skip to main content
VulnerabilityPublished

CVE-2026-117601: Electrum · Malicious server can replace a just-broadcast tx and try to trick user into RBF-ing it

Affects electrumSource GCVE Database

0
Authoritative record:CVE-2026-117601· Critical 9.3

Not known to be exploited · CVSS 9.3 Critical : upgrade to 4.8.3 as a priority.

Data as of 28 Oct 2026, 22:28 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.8.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade electrum to 4.8.3.

Affected software

ProductAffectedFixed in
PyPIelectrumAffected
  • <4.8.3
Fixed in
  • 4.8.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Electrum to version 4.8.3 or later, which includes a fix that verifies signatures of wallet-owned inputs in mempool transactions. Until upgrading, users must manually verify output addresses and amounts before signing any transaction, especially when fee-bumping. Clients connecting only to trusted servers (e.g., self-run servers) are not affected. No other mitigations are specified.

Description

Electrum versions prior to 4.8.3 are vulnerable to a malicious server attack where the server can replace a just-broadcast transaction with a conflicting transaction containing the attacker's output address. This attack exploits the client's trust in the server's mempool data and the lack of signature verification for unconfirmed transactions, potentially tricking users into fee-bumping a fraudulent transaction and losing funds. The issue is fixed in Electrum 4.8.3 by verifying signatures of wallet-owned inputs in mempool transactions before adding them to the local history.

References

Community reviews

Loading reviews…