Electrum before 4.7.2 contains a spending limit bypass vulnerability in the Nostr Wallet Connect plugin that allows malicious NWC clients to exceed daily_limit_sat by exploiting non-atomic budget checks and millisatoshi truncation. Attackers can send concurrent pay_invoice requests that pass budget_allows_spend() before add_to_budget() runs, or repeatedly pay msat amounts that are floored to whole satoshis, to drain funds beyond the limit.
CVE-2026-117603
MEDIUMPre-NVD 4.34.3
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 4.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-27. A secondary CVSS source baseline 4.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-110852 (ENISA EUVD) · GHSA-98mp-7r7x-725c (GitHub Security Advisories)Source: ENISA EUVD
4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 4.3
- EG Score
- 4.3MEDIUMhigh confidence
- EG Risk
- 19EG Risk 19/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity43% × 45%Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 9th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 27, 2026
Last Modified
November 2, 2026
Advisory Details (4)
Auto-updated Oct 27, 2026Patch available. Sources: github, github_commit.
Web page
Electrum before 4.7.2 Nostr Wallet Connect Plugin Daily Spending Limit Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/electrum-before-4.7.2-nostr-wallet-connect-plugin-daily-spending-limit-bypassGitHub commit
commit 3956bff0684f (spesmilo/electrum)
Fix landed in spesmilo/electrum commit 3956bff0684f — awaiting tagged release
https://github.com/spesmilo/electrum/commit/3956bff0684f6060fbe8c823c3ee921928cdcaa5GitHub commit
commit 5222374046d2 (spesmilo/electrum)
Fix landed in spesmilo/electrum commit 5222374046d2 — awaiting tagged release
https://github.com/spesmilo/electrum/commit/5222374046d2a92da371d46c79ce0e61e7e2a42dGitHub advisoryMentions a patch (unverified)
Nostr Wallet Connect plugin: daily spending limit bypass · Advisory · spesmilo/electrum · GitHub
https://github.com/spesmilo/electrum/security/advisories/GHSA-q7m2-785w-r585Vendor Advisories for CVE-2026-117603(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| electrum | 4.5.8+ds-6 ... 4.8.1+dfsg-1~bpo13+1 (14 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 23× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-11 06:54 UTCEchelonGraph re-scored
- 2026-11-11 06:54 UTCGHSA enrichmentGHSA-98mp-7r7x-725c · GitHub severity CRITICAL · GitHub CVSS 4.3
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-04 01:48 UTCEchelonGraph re-scored
- 2026-11-04 01:48 UTCGHSA enrichmentGHSA-98mp-7r7x-725c · GitHub severity CRITICAL · GitHub CVSS 4.3
- 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-11-02 16:28 UTCEchelonGraph re-scored
- 2026-11-02 16:28 UTCGHSA enrichmentGHSA-98mp-7r7x-725c · GitHub severity CRITICAL · GitHub CVSS 4.3
- 2026-11-02 16:17 UTCEchelonGraph re-scored
- 2026-11-02 16:17 UTCGHSA enrichmentGHSA-98mp-7r7x-725c · GitHub severity CRITICAL · GitHub CVSS 4.3
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-27 16:09 UTCEchelonGraph re-scored
Show 5 moreShow fewer
- 2026-10-27 16:09 UTCGHSA enrichmentGHSA-98mp-7r7x-725c · GitHub severity CRITICAL · GitHub CVSS 4.3
- 2026-10-27 14:29 UTCEchelonGraph re-scored
- 2026-10-27 14:01 UTCENISA EUVD ID recordedEUVD-2026-110852 · Source: ENISA EUVD
- 2026-10-27 13:37 UTCEchelonGraph re-scoredFirst assessed: 4.3 MEDIUM
- 2026-10-27 13:34 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
5 shownDebian:14:electrum
Same CWE
10 shownCWE-367
Frequently asked(5)
What is CVE-2026-117603?
CVE-2026-117603 is a medium-severity vulnerability; its CVE record was published on October 27, 2026. Electrum before 4.7.2 contains a spending limit bypass vulnerability in the Nostr Wallet Connect plugin that allows malicious NWC clients to exceed daily_limit_sat by exploiting non-atomic budget checks and millisatoshi truncation. Attackers can send concurrent pay_invoice requests that pass…
When was CVE-2026-117603 made public?
CVE-2026-117603 was made public on April 28, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 27, 2026. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-117603 actively exploited?
CVE-2026-117603 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-117603?
CVE-2026-117603 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-117603?
A fix for CVE-2026-117603 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-117603 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-117603
Is Your Infrastructure Affected by CVE-2026-117603?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.