Skip to main content

Moxa MGate CVE-2026-86325

| EUVDEUVD-2026-91371 CRITICAL
Stack-based Buffer Overflow (CWE-121)
2026-10-02 Moxa GHSA-gf54-rrcc-vgxp
9.4
CVSS 4.0 · Vendor: Moxa
View

Attack ChainAIDerived

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

  1. Access
    Authenticate as read-only web user
  2. Delivery
    Send account management request
  3. Exploit
    Overflow account_name stack buffer
  4. Execution
    Corrupt execution flow
  5. Impact
    Read credentials / modify memory / crash device

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

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

Exploitation Conditions

Exploitation requires an authenticated session as a low-privilege read-only user on the MGate protocol gateway's web management interface (PR:L), reached over the network with no user interaction. The specific trigger is the account_name parameter in account-management requests, which lacks sufficient length validation; supplying an over-length value overflows an internal stack buffer. The principal limiting factor is the authentication requirement - the attacker must already possess valid (even read-only) credentials - which constrains purely anonymous remote exploitation, though read-only accounts typically present a low barrier in practice.

Impact

This is a genuinely high-priority vulnerability, though the raw 9.4 score slightly overstates the ease of exploitation. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) confirms network-reachable, low-complexity exploitation requiring no user interaction, but PR:L means the attacker must first hold valid credentials - specifically a read-only web-management account. The impact ceiling is severe: the stack overflow enables memory disclosure (credentials), arbitrary memory modification, and denial of service, which maps to the VC:H/VI:H/VA:H impact set. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The realistic risk driver here is the combination of a very low authentication bar (read-only accounts are often shared or weakly protected in OT environments) with full device compromise potential on a protocol gateway that bridges industrial networks. Note the vendor-supplied 4.0 vector asserts subsequent-system impact (SC/SI/SA:H); the description only documents impact to the gateway itself, so the cross-system impact claim should be verified against the vendor advisory rather than assumed.

Exploit ScenarioDerived

An attacker who has obtained or been granted a low-privilege read-only account on the MGate web management interface submits an account-management request containing an oversized account_name value. The overflow corrupts the stack, letting the attacker read credentials from device memory, overwrite memory to alter execution flow, or crash the gateway. No public exploit code is identified at time of analysis, so this would currently require original exploit development.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 02, 2026

Stack-based buffer overflow in the web management interface of Moxa MGate MB3170 and MB3270 series protocol gateways lets an attacker who already holds a valid, low-privilege read-only account corrupt program execution by submitting an over-length account_name value in an account-management request. Because the overwritten stack data can be leveraged to read device memory (including stored credentials), modify arbitrary memory, and crash or hang the device, the impact spans confidentiality, integrity, and availability of both the gateway and the downstream systems it bridges. No public exploit code or active exploitation has been observed (no CISA KEV listing; no public exploit identified at time of analysis), and the realistic barrier is the requirement for valid credentials rather than anonymity - though read-only accounts are often weakly protected or shared, which is why the issue still warrants urgent attention.

RemediationAI

No vendor-released patch version is identified in the available data at time of analysis, so the first action is to consult Moxa security advisory MPSA-269540 (https://www.moxa.com/en/support/product-support/security-advisory/mpsa-269540-cve-2026-86325,-cve-2026-86326-two-vulnerabilities-in-protocol-gateways) for the current firmware update and version mapping for the MGate MB3170 and MB3270 series, and to apply that firmware as soon as it is published. Until a fix can be deployed, compensating controls should focus on the two preconditions this exploit needs - network reachability of the web management interface and possession of a valid (even read-only) account: restrict the management interface to a dedicated, firewalled management VLAN or OT management segment so that ordinary OT/IT hosts cannot reach it (trade-off: remote administration and monitoring must be performed from a jump host, which adds operational friction but eliminates the network attack path); disable or block the HTTP/HTTPS management service on any unit that does not require it (trade-off: SNMP or serial/console management must be used instead, and some monitoring tooling may break); where the platform permits it, remove or disable account-management privileges and unused accounts so that only the minimum necessary administrative identities exist, since the trigger is an account-management request and read-only roles are the stated exploitation prerequisite (trade-off: legitimate user administration must be performed by a smaller set of privileged operators); and avoid reusing credentials across OT devices, because the disclosed memory can contain stored credentials that would otherwise enable lateral movement. It is important to note that applying these workarounds does not remove the underlying memory-corruption bug - they reduce exposure only, and firmware remediation remains the definitive fix.

Affected VersionsENISA

MGate MB3270 Series 1.0 ≤4.7
MGate MB3170 Series 1.0 ≤4.7

Affected Packages

euvd mgate_mb3170_series no fix
euvd mgate_mb3270_series no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

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

Technical ContextAI · show details

The flaw is a classic CWE-121 stack-based buffer overflow arising from missing or insufficient length validation of the account_name parameter handled by the protocol gateways' account management interface. When an account-management request is parsed, the attacker-controlled account name is copied into a fixed-size buffer allocated on the stack without bounding the copy length, so an over-length value overwrites adjacent stack memory - including saved registers and the return address - and lets the attacker redirect program execution flow. The affected code path is reachable over the network through the device's embedded web management application, which is why the assessed vector is AV:N/AC:L/PR:L/UI:N with unchanged scope (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), while the vendor's CVSS 4.0 scoring (9.4) additionally records subsequent-system impact (SC:H/SI:H/SA:H). That subsequent-system component reflects the role of these devices: MGate MB3170/MB3270 units act as Modbus/DNP3/protocol conversion gateways sitting between OT networks and supervisory systems, so memory disclosure of stored credentials or arbitrary memory corruption on the gateway can expose or destabilize the industrial control paths behind it. The supplied CPEs (cpe:2.3:a:moxa:mgate_mb3170_series:*:*:*:*:*:*:*:* and cpe:2.3:a:moxa:mgate_mb3270_series:*:*:*:*:*:*:*:*) confirm the affected product families but, because the version components are wildcarded, the publicly available metadata does not pin down which firmware builds are vulnerable; the authoritative source for firmware version detail is the Moxa advisory MPSA-269540.

Know when Mgate Mb3170 Series gets its next vulnerability

  • 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 (Moxa) PRIMARY 9.4 CRITICAL
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
vuln.today AI 8.8 HIGH

Network-reachable web interface (AV:N/AC:L), authenticated read-only user (PR:L), no interaction; overflow yields memory read, write, and crash on the device, so C/I/A:H with impact confined to the gateway (S:U).

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

Primary rating from Vendor (Moxa).

CVSS VectorVendor: Moxa

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Moxa MGate MB3170 and MB3270 series protocol gateways are affected by a critical stack-based buffer overflow in their web management interface. An attacker with a valid low-privilege read-only account could exploit this to read sensitive device memory (including stored credentials), modify arbitrary memory, and crash or hang the device, impacting confidentiality, integrity, and availability of both the gateway and the downstream systems it bridges. Leadership should prioritize this because these gateways often connect critical OT/ICS networks, and a compromise could lead to operational disruption, data loss, and lateral movement into sensitive environments, though no public exploit identified at time of analysis.

Business Impact: Severe
Compensating Controls

Interim mitigations include: restricting network access to the web management interface to trusted IPs, disabling the web management interface if not required, enforcing strong unique credentials for all accounts (particularly read-only accounts), monitoring for anomalous account-management requests, segmenting the gateway network, and deploying IDS/IPS signatures.

Threat Intelligence Overview

EPSS Score
0.3%
Top 75% exploitable
Prevalence
Low
industrial Modbus-to-Ethernet gateway, niche OT/ICS deployment footprint
Data Quality
4 sources
Confidence: Medium

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 No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

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

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

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