Skip to main content
VulnerabilityPublished

CVE-2026-86325: Moxa MGate MB3170 Series · Stack-based Buffer Overflow

Affects Moxa MGate MB3170 SeriesSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.4 Critical.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-02.

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
MoxaMGate MB3170 SeriesAffected
  • >=1.0 <=4.7
Fixed in–
MoxaMGate MB3270 SeriesAffected
  • >=1.0 <=4.7
Fixed in–

AI-suggested

Until a fix is available, restrict authenticated access to the web management interface to trusted users only and monitor for unusual activity. Avoid exposing the management interface to untrusted networks.

Description

CVE-2026-86325 is a critical stack-based buffer overflow vulnerability in the account management interface of Moxa MGate MB3170 Series protocol gateways. It arises from insufficient validation of the length of the 'account_name' parameter during account management requests. An authenticated read-only user can exploit this by supplying an overly long account name, leading to corruption of program execution flow. Exploitation can result in unauthorized reading of sensitive device memory, including credentials, arbitrary memory modification, and disruption of device availability.

References

Community reviews

Loading reviews…