Persistent code execution via unverified firmware images
Published Oct 2, 2026 · Updated Oct 2, 2026
Improper firmware signature verification in Moxa MGate MB3170 and MB3270 Series 1.0 allows attackers to install modified firmware. The firmware update path accepts an image without adequately verifying its cryptographic authenticity; the precise verification failure has not been publicly described. Exploitation requires high privileges and access to the update interface, after which unauthorized code can persist across firmware updates and disrupt the gateway.
Summary
What happened
Improper firmware signature verification in Moxa MGate MB3170 and MB3270 Series 1.0 allows attackers to install modified firmware. The firmware update path accepts an image without adequately verifying its cryptographic authenticity; the precise verification failure has not been publicly described. Exploitation requires high privileges and access to the update interface, after which unauthorized code can persist across firmware updates and disrupt the gateway.
The record
- CVE
- CVE-2026-86326
- Published
- Oct 2, 2026
- Updated
- Oct 2, 2026
- Vendor
- Moxa
- Product
- MGate MB3270 Series
- Classifications
- T1601.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Oct 2, 2026CVE publishedPublication date reported by the CVE source.
- Oct 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started