Skip to main content

MultiversX multisig-improved CVE-2026-106511

| EUVDEUVD-2026-93662 CRITICAL
Missing Authentication for Critical Function (CWE-306)
2026-10-06 cret@cert.org GHSA-vxx8-8p7v-9mvp
9.8
CVSS 3.1 · Vendor: cert
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain or compromise Proposer-role account
  2. Delivery
    Submit action barred for Proposers
  3. Exploit
    Missing authorization check passes
  4. Execution
    Execute fund transfer without signatures
  5. Impact
    Drain 100% of EGLD/ESDT balance

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to control an account that has been assigned the Proposer role on a deployed instance of the MultiversX multisig-improved smart contract built from the vulnerable commit (2e6dbea40f9b8ac165572a9efd4304804762a299); the flaw is the absence of an independent authorization check that should bar Proposers from fund-moving actions. Limiting factors: the attacker is not a fully anonymous outsider - they must already hold the Proposer role on the specific contract, and the target must be a multisig deployment using the unpatched code. No board signatures or additional user interaction are required once the role is held, and the full balance is drainable in two transactions.

Impact

The input CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) rates this as critical and network-exploitable with no privileges, consistent with CWE-306 (Missing Authentication/Authorization for a Critical Function) and the 'Authentication Bypass' tag. However, there is an important internal conflict: the description states the actor must be 'any account with the Proposer role,' which is a pre-assigned contract role - so this is really a broken-authorization / privilege-escalation flaw (a Proposer doing what only signers should do), not a fully anonymous unauthenticated action. The PR:N scoring is defensible only if one treats the Proposer role as an intended low-trust participant who should never be able to move funds; in practice the attacker must already hold that role, which narrows the exploit population - verify this nuance against the vendor advisory. Signals diverge: a POC exists publicly (a gist) and technical impact is total (100% of EGLD/ESDT drained in two transactions with zero signatures), yet EPSS is very low (0.15%, 3rd percentile) and the CVE is NOT in CISA KEV, indicating no evidence of widespread automated exploitation. On balance this is a genuine high-severity correctness/security defect in on-chain funds handling with a working POC, but real-world mass exploitation risk is tempered by the requirement to hold a Proposer role on a specific vulnerable multisig deployment rather than attacking the internet at large.

Exploit ScenarioDerived

An attacker who has been granted (or has compromised an account holding) the Proposer role on a deployed multisig-improved contract issues two transactions that invoke fund-moving actions the Proposer should be barred from, transferring the full EGLD/ESDT balance to an attacker-controlled address with no board signatures. Publicly available POC code exists (a GitHub gist), lowering the skill needed; the low CVSS attack complexity (AC:L) means no special timing or race conditions are required once the role is held.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
1 PoC candidate (unverified) No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Missing authorization checks in the MultiversX 'multisig-improved' reference smart contract (mx-multisig-and-modules) allow an account holding the Proposer role to unilaterally move funds, draining 100% of a deployed contract's EGLD/ESDT balance in as few as two transactions with zero board signatures. The flaw is a CWE-306 missing-authentication issue in the fund-moving execution path; exploitation requires the attacker to already hold the Proposer role on a specific vulnerable deployment (assessed as PR:L, authenticated), not fully anonymous access, and publicly available exploit code exists, though there is no confirmed active exploitation (no CISA KEV) and EPSS is only 0.15% (3rd percentile). Deployments built from the affected commit are fully exposed once a Proposer-role account is compromised or malicious.

RemediationAI

No vendor-released patch or fixed version is identified in the provided data; treat the referenced commit (2e6dbea40f9b8ac165572a9efd4304804762a299) as vulnerable and check the mx-multisig-and-modules repository (https://github.com/multiversx/mx-multisig-and-modules) for an updated commit that adds the missing independent authorization check, then rebuild and redeploy from that commit. Because on-chain contract code is immutable, remediation for already-deployed instances is not an in-place upgrade: operators must deploy the corrected contract and migrate funds and role assignments to it, and should consider draining the vulnerable contract's EGLD/ESDT balance to a safe address until migration completes. Where redeployment is not immediately possible, apply compensating controls: remove or tightly restrict assignment of the Proposer role so only a single, heavily monitored and externally protected account holds it (trade-off: legitimate proposal workflows are disrupted, and a compromise of that account still drains the contract, so it is a partial mitigation only); minimize the balance held directly by the vulnerable contract, keeping most funds in a separate treasury contract with no active Proposer; and monitor on-chain activity for the characteristic two-transaction drain pattern so the fund movement can be front-run or frozen by the board. Note that public proof-of-concept code is available (https://gist.github.com/x01griax/c03f4be898dc55ccf3bab667c83c7312), so prioritize assessment of any deployment built from the affected commit; consult the EUVD advisory (https://nvd.nist.gov/vuln/detail/CVE-2026-106511) and the vendor repository for any subsequent patch guidance.

Affected VersionsENISA

multisig-improved GitHub commit 2e6dbea40f9b8ac165572a9efd4304804762a299

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the MultiversX on-chain multisig smart contract reference implementation, written in Rust and compiled to WebAssembly for the MultiversX (Elrond) blockchain using the MultiversX smart contract SDK. On-chain multisig systems like this typically separate roles: board members who must collectively sign fund-moving actions and proposers/signers who can only initiate or endorse proposals. The root cause is CWE-306 (Missing Authentication for Critical Function): the implementation lacks an independent authorization check that should expressly bar a Proposer from performing actions the system explicitly disallows, so the Proposer path reaches fund-transfer logic without validating that the caller is authorized for that critical function. The result is that a single Proposer-role account can execute a balance-draining transfer sequence in two transactions without the multi-signature quorum that the contract design assumes. The input CVSS vector claims PR:N, but the reviewed exploitation conditions and our assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H) indicate the attacker must already hold the Proposer role, making this a privilege-abuse/authorization-bypass issue rather than an unauthenticated remote compromise. No CPE strings were supplied; the EUVD-mapped affected artifact is the GitHub commit 2e6dbea40f9b8ac165572a9efd4304804762a299.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (cert) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

Attacker must hold the Proposer role so PR:L not PR:N; blockchain call is remote (AV:N) with no interaction; impact is fund theft (I:H/A:H) with no data disclosure (C:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (cert).

CVSS VectorVendor: cert

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Oct 07, 2026 - 18:22 NVD
9.8 (CRITICAL)
CVE Published
Oct 06, 2026 - 19:18 cve.org
CRITICAL 9.8
CVE Published
Oct 06, 2026 - 19:18 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

MultiversX's multisig-improved (repository: mx-multisig-and-modules) reference implementation of their on-chain multisig smart contract system contains a vulnerability where a missing independent authorization check allows any account with the Proposer role to perform explicitly barred actions. This vulnerability allows the Proposer role to move funds alone, draining 100% of a contract's EGLD/ESDT balance in two transactions with zero signatures.

Technical POC Analysis

The bug class is CWE-306: missing independent authorization for a critical fund-moving action.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Latest POC

1 PoC candidate from github (unverified)

Sign in to open the public PoC links collected for this CVE.

Executive ViewAI

Why It Matters

MultiversX's 'multisig-improved' reference smart contract (mx-multisig-and-modules) contains a missing-authorization flaw that lets any account already holding the Proposer role drain 100% of a deployed contract's EGLD and ESDT holdings in as few as two transactions, with no board approval required. Any treasury, DeFi vault, or DAO deployment built from the affected commit is fully exposed the moment a Proposer-role key is compromised or turned malicious, undermining the governance guarantees organizations rely on and creating direct, irreversible loss of funds. Leadership should treat this as a critical custody risk requiring immediate credential review and migration planning, even though exploitation is not confirmed and EPSS remains low at 0.1%.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include revoking or tightly limiting the Proposer role, enforcing off-chain co-signing and manual review for every fund-moving proposal, monitoring on-chain for Proposer-initiated transfers, rotating keys for any account retaining the role, and migrating at-risk balances to an alternative multisig implementation that does not share the vulnerable execution path.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
niche blockchain-specific reference smart contract, limited production deployments
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

69
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy