# CVE-2026-106511: CVE-2026-106511

> Attackers with Proposer role can drain all funds from MultiversX multisig contracts due to missing authorization checks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-vxx8-8p7v-9mvp

## What is CVE-2026-106511?

CVE-2026-106511 is a critical missing authorization vulnerability in MultiversX Labs S.R.L. multisig-improved, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization), CWE-863 (Incorrect Authorization), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-106511?


## How do I fix CVE-2026-106511?

No fix has been published for CVE-2026-106511 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106511 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-106511 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106511 and fix it if it is affected.

What it is: CVE-2026-106511 is a critical missing authorization vulnerability in MultiversX Labs S.R.L. multisig-improved, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-106511 exists.

Affected product: MultiversX Labs S.R.L. multisig-improved. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106511/ (Markdown: https://insights.sbomify.com/CVE-2026-106511/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106511
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106511
- OSV: https://osv.dev/vulnerability/CVE-2026-106511

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106511/
Summaries are generated and may contain mistakes; the official description above is the record.