CVE-2026-117601

Electrum before 4.8.3 Missing Signature Verification of Mempool Transactions

Published Oct 27, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
Electrum before 4.8.3 fails to verify signatures of wallet-owned inputs in unconfirmed mempool transactions, allowing malicious servers to replace a just-broadcast transaction with a conflicting one. Attackers can swallow the user's transaction and display an invalid zero-fee copy paying an attacker address, tricking users into RBF fee-bumping and signing it.

Analysis

AI-generated

Technical impact

Electrum versions prior to 4.8.3 do not verify the signatures of wallet‑owned inputs in unconfirmed mempool transactions. This flaw allows an attacker who controls or compromises a server to replace a user’s broadcast transaction with a conflicting one. By broadcasting a zero‑fee copy that pays an attacker address, the server can entice the user to perform a replace‑by‑fee (RBF) bump, causing the user to sign and submit a transaction that transfers funds to the attacker.

Affected Systems

The vulnerability affects the Electrum wallet distributed by Specmilo. All releases before version 4.8.3 are vulnerable; version 4.8.3 and later include the signature verification fix.

Risk and Exploitability

The CVSS score of 9.3 indicates a high severity. EPSS data is not available, so the current exploitation probability is unknown, but the lack of signature validation makes local and remote exploitation likely as soon as a malicious or untrusted server is contacted. The vulnerability is not listed in the CISA KEV catalog, yet the attack does not require a sophisticated payload—any compromised or malicious Electrum server can perform the transaction swap. The likely attack vector is a server‑side substitution of mempool transactions that the client accepts without verification.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Electrum wallet to version 4.8.3 or later, which implements signature verification for mempool transactions.
  • Configure Electrum to connect only to trusted, verified Lightning or full‑node servers, or use network certificates to validate the server identity.
  • Avoid or disable RBF fee‑bumping for transactions received from untrusted sources until the transaction is confirmed and signature‑verified.

Generated by OpenCVE AI on October 27, 2026 at 14:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-6jp4-8v48-cc5v Electrum: Malicious server can replace a just-broadcast tx and try to trick user into RBF-ing it
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Electrum before 4.8.3 fails to verify signatures of wallet-owned inputs in unconfirmed mempool transactions, allowing malicious servers to replace a just-broadcast transaction with a conflicting one. Attackers can swallow the user's transaction and display an invalid zero-fee copy paying an attacker address, tricking users into RBF fee-bumping and signing it.
Title Electrum before 4.8.3 Missing Signature Verification of Mempool Transactions
First Time appeared Electrum
Electrum electrum
Weaknesses CWE-347
CPEs cpe:2.3:a:electrum:electrum:*:*:*:*:*:*:*:*
Vendors & Products Electrum
Electrum electrum
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': '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'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 28, 2026, 4:16 PM
Reserved
Oct 27, 2026, 1:04 PM
Status
Awaiting Analysis
Published
Oct 27, 2026, 2:16 PM
Modified
Oct 28, 2026, 5:18 PM
Severity
Important
Public date
Oct 27, 2026, 1:09 PM