# CVE-2026-106705: Privilege escalation in n/a

> A logged-in user with edit permissions can escalate privileges by modifying their own role's menu access due to improper access control checks.

- **Severity:** High 8.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-q45x-9wpf-qjgr

## What is CVE-2026-106705?

CVE-2026-106705 is a high-severity vulnerability in n/a, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ELADMIN (eladmin-mp) up to 2.7 contains an improper access control vulnerability in the role management module. The endpoint PUT /api/roles/menu (RoleController.updateRoleMenu) authorizes the request only by comparing the target role's level with the caller's minimum level. The application neither validates the granted menu set nor prevents a caller from modifying its own role. A logged-in non-admin user whose role holds the delegated `roles:edit` permission can submit its own role id together with an arbitrary list of menu ids.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-106705 being exploited?

There is no known exploitation of CVE-2026-106705 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106705 is a high-severity vulnerability in n/a, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106705 in the wild and no public exploit code.

Affected product: n/a. 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-106705/ (Markdown: https://insights.sbomify.com/CVE-2026-106705/index.md)
```

## Sources

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

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