# CVE-2026-86325: Memory corruption in MGate MB3170 Series

> Authenticated attackers can exploit a stack buffer overflow in Moxa MGate gateways to read memory, modify data, or cause denial of service.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-gf54-rrcc-vgxp

## What is CVE-2026-86325?

CVE-2026-86325 is a critical memory corruption vulnerability in Moxa MGate MB3170 Series, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A stack-based buffer overflow vulnerability exists in protocol gateways' account management interface. The vulnerability is caused by insufficient length validation of the `account_name` parameter when processing account management requests. An attacker authenticated as a read-only user to the web management interface could supply a specially crafted account name that exceeds the size of the internal stack buffer, resulting in corruption of program execution flow. Successful exploitation could allow an attacker to read sensitive information from device memory, including credentials, modify arbitrary memory contents, and disrupt device availability.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-86325 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86325 is a critical memory corruption vulnerability in Moxa MGate MB3170 Series, published on 2 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-86325 in the wild and no public exploit code.

Affected product: Moxa MGate MB3170 Series. 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-86325/ (Markdown: https://insights.sbomify.com/CVE-2026-86325/index.md)
```

## Sources

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

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