Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain high-privilege gateway access
-
DeliveryReach firmware update interface
-
ExploitUpload crafted unsigned firmware image
-
ExecutionDevice installs without signature check
-
PersistMalicious firmware executes
-
ImpactPersist across future updates
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | Exploitation requires the attacker to already hold high-privilege (administrative) access to the device's firmware update interface on a Moxa MGate MB3170 or MB3270 series gateway, and to be able to reach that interface over the network. The core enabling condition is the device's failure to validate the cryptographic signature/authenticity of firmware images prior to installation, so any image the privileged interface accepts is flashed regardless of origin. Limiting factors that reduce real-world risk: the PR:H requirement means an unprivileged or external attacker cannot exploit this directly without first gaining admin credentials or chaining another flaw; network segmentation that isolates the OT management plane and restricting access to the update interface materially constrain exploitability. No end-user interaction (UI:N) is required once privileged access is held. |
| Impact | This is a genuine but access-gated integrity flaw rather than a mass-exploitation threat. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N, VC:H/VI:H/VA:H) scores 8.6 (High) and the high vulnerable-system impact is credible for a firmware-trust failure: unauthorized firmware yields full code execution and durable persistence. However, the single most important mitigating signal is PR:H - exploitation requires an attacker who already holds high-privilege access to the firmware update interface, which substantially narrows the realistic attacker population. No EPSS score, CISA KEV listing, or public exploit code was provided in the intelligence, so there is no evidence of widespread or opportunistic exploitation; this reads as a high-CVSS issue whose real-world urgency is tempered by the privilege precondition. Note a mild tension worth verifying: the vector marks AV:N (network) and UI:N, implying the firmware update interface is remotely reachable, yet the required high privileges mean the practical threat is primarily an already-authenticated administrator or an attacker who has first compromised management credentials. Treat prioritization as elevated for exposed/internet-facing OT management planes and moderate for properly segmented deployments. |
| Exploit ScenarioDerived | An attacker who has obtained high-privilege access to a Moxa MGate gateway's firmware update interface (e.g., via compromised admin credentials or a chained authentication flaw) uploads a maliciously modified firmware image. Because the device does not verify the cryptographic signature of the image before installation, the tampered firmware is accepted and flashed, giving the attacker code execution and a persistent foothold that survives subsequent updates. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Firmware images pushed to Moxa MGate MB3170 and MB3270 series protocol gateways are not cryptographically validated before installation, so a modified or counterfeit image is flashed with the same trust as a vendor-signed one. Exploitation requires an attacker to already hold high-privilege (administrative) access to the device's firmware update interface and to reach it over the network; once that access exists, no additional weakness is needed and no user interaction is required. Successful abuse yields code execution on the gateway plus persistence across subsequent firmware updates, but the impact is confined to the device itself rather than downstream OT systems. There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score supplied. This is a genuine but access-gated integrity flaw rather than a mass-exploitation threat.
RemediationAI
The only complete fix is vendor firmware that enforces cryptographic verification of firmware images; the available input does not specify a patched version number, so obtain the fixed release for the specific MGate MB3170 or MB3270 model directly from 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), which also covers the companion CVE-2026-86325, and treat absence of a listed version as 'not confirmed' rather than 'not patchable'. Because exploitation is gated on administrative access to the firmware update interface, the highest-value compensating controls are access controls on that interface: place MGate management/update services on an isolated OT management VLAN, block the update/web management ports from business, wireless, and internet-facing segments via firewall or ACL rules, and disable remote management where the deployment permits. The trade-off is that this forces firmware updates to be performed from a jump host inside the trusted segment or locally, adding operational effort and delaying emergency patching. Additionally, replace default and shared credentials with unique strong administrator passwords and audit accounts with firmware-update rights, since those accounts are the prerequisite for exploitation; this reduces but cannot eliminate risk if an authorized operator is malicious or a credential is stolen. Where feasible, verify firmware image hashes or signatures out-of-band against Moxa-published checksums before flashing, and monitor device configuration/firmware version reporting for unexpected reversions or changes as a detection measure; out-of-band verification is manual, does not scale well across large fleets, and is prone to human error. Network isolation and credential hardening are partial mitigations only, as they reduce the likelihood of an attacker reaching the prerequisite privileged state rather than remediating the missing signature check itself.
Affected VersionsENISA
Affected Packages
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 root cause is CWE-347 (Improper Verification of Cryptographic Signature): the firmware update path on Moxa MGate MB3170 and MB3270 series protocol gateways accepts an image without properly validating its cryptographic authenticity, meaning signature/trust-chain checks are absent or can be bypassed prior to flashing. The CVSS 4.0 vector in the CVE record (AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) aligns with the independent CVSS 3.1 assessment (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H): network-reachable, no special attack conditions, no user interaction, but gated behind high privileges, with high confidentiality, integrity, and availability impact on the affected device and no assessed impact to subsequent systems. MGate MB3170/MB3270 units are serial-to-Ethernet/Ethernet-to-serial protocol gateways commonly deployed on OT networks to bridge Modbus and other industrial protocols to plant systems, so the relevant attack surface is the device management/firmware update interface rather than the process-control traffic path. The affected-product CPEs (cpe:2.3:a:moxa:mgate_mb3170_series:* and cpe:2.3:a:moxa:mgate_mb3270_series:*) are version-wildcarded, i.e. no fixed version is enumerated in the feed data. The Moxa advisory MPSA-269540 covers this issue jointly with CVE-2026-86325, indicating two distinct defects addressed in the same bulletin. Note that feed tags for this record include 'Authentication Bypass' and 'Jwt Attack' terminology, which is not corroborated by the CWE-347 signature-verification description or the assessed vector; the advisory text and CWE should be treated as authoritative for scoping.
Know when Jwt Attack 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Firmware update requires administrative access so PR:H; interface is network-reachable (AV:N) with no user interaction, and malicious firmware fully compromises C/I/A.
Primary rating from Vendor (Moxa).
CVSS VectorVendor: Moxa
DescriptionCVE.org
An improper verification of cryptographic signature vulnerability exists in protocol gateways because the device does not properly verify the cryptographic authenticity of firmware images before installation. An attacker with high privileges and access to the firmware update interface could provide a specially crafted or modified firmware image, causing it to be installed on the device. Successful exploitation could allow the attacker to execute unauthorized code, compromise the integrity and availability of the device, and persist malicious modifications across subsequent firmware updates.
Executive ViewAI
Moxa MGate MB3170 and MB3270 series protocol gateways are affected by a high-severity firmware integrity flaw (CVE-2026-86326) that allows an attacker with existing administrative access to install modified firmware, resulting in code execution and persistence on the device. While no public exploit identified at time of analysis and exploitation is access-gated, the absence of a vendor patch means OT asset owners in industrial environments must act to protect these gateways. Leadership should prioritize network segmentation and strict access controls to mitigate risk until a patch is available.
No vendor-released patch identified at time of analysis. Interim mitigations: isolate management interfaces via network segmentation; enforce least-privilege administrative access and multi-factor authentication where supported; monitor and log all firmware update attempts; verify firmware integrity using vendor-provided checksums before installation.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Jwt Attack
View allWhy is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update
Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke
Authentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,
Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT
Authentication and authorization bypass in fast-jwt 6.2.0 through 6.2.4 (npm, NearForm) lets a remote, unauthenticated a
A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti
A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27
A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
EUVD-2026-91373
GHSA-pccp-468g-6mp8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB