Skip to main content

Moxa AIG-302 EUVDEUVD-2026-102594

| CVE-2026-109813 HIGH
Use of Hard-coded Cryptographic Key (CWE-321)
2026-10-16 Moxa GHSA-4w88-hm3w-rh83
8.6
CVSS 4.0 · Vendor: Moxa
View

Attack ChainAIDerived

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

  1. Access
    Gain adjacent network access to OT segment
  2. Exploit
    Extract hard-coded private key from sysman firmware
  3. Execution
    Intercept or MITM device communications
  4. Impact
    Decrypt and tamper with traffic

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
Exploitation Conditions

Exploitation requires adjacent network access (AV:A) - the attacker must be on the same local/logical network segment as the Moxa AIG-302 Series device (e.g., the industrial LAN), not the open internet, which is the primary limiting factor. No authentication, privileges, or user interaction are needed (PR:N/UI:N) once that network position is obtained. The attacker must obtain the hard-coded private key material embedded in /usr/bin/sysman - trivially recoverable by reverse-engineering the firmware of any affected unit since the key is static across devices - and then be positioned to intercept the target's communications to decrypt or tamper with them. Impact is limited to confidentiality and integrity of communications; there is no availability impact (VA:N).

Impact

This is a credible, moderately high-priority OT/ICS risk rather than an inflated high-CVSS issue, but it is tempered by access constraints. The vendor-supplied CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N) scores 8.6 and indicates an unauthenticated, low-complexity attack with no user interaction yielding high confidentiality AND integrity impact - consistent with CWE-321 (hard-coded cryptographic key), where a shared/static private key embedded in /usr/bin/sysman lets an attacker decrypt or forge protected communications. The key limiting signal is the Adjacent (AV:A) attack vector: the attacker must be on the same logical network segment (e.g., the local industrial LAN) rather than exploiting across the open internet, which meaningfully narrows the exposure to insiders, pivoted hosts, or anyone with access to the OT network. No EPSS score, CISA KEV listing, or public POC was provided in the intelligence, so there is no evidence of active exploitation or weaponization; the real-world probability of mass exploitation is currently low despite the high severity rating. Because hard-coded keys are typically identical across all units of an affected firmware line, the flaw is systemic (one extracted key compromises the whole fleet), which raises long-term risk if the key is ever published. Net: prioritize patching for exposed/flat OT networks, but treat widespread opportunistic exploitation as unlikely until key material or a POC surfaces.

Exploit ScenarioDerived

An attacker with a foothold on the same industrial network segment as a Moxa AIG-302 gateway extracts the hard-coded private key from the sysman binary (or an identical unit's firmware) and uses it to passively decrypt intercepted traffic or actively machine-in-the-middle the device's communications, breaking confidentiality and tampering with integrity. No authentication or user interaction is required, but adjacent network positioning is. No public exploit identified at time of analysis, so an attacker would need to reverse-engineer the firmware themselves.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 16, 2026

Hard-coded cryptographic key material embedded in the /usr/bin/sysman binary of Moxa's AIG-302 Series industrial computers enables an unauthenticated attacker who already sits on the same local or logical network segment to recover the static private key and use it to decrypt or tamper with the device's protected communications. The key is identical across all affected units and is trivially extractable by reverse-engineering shipped firmware, so the confidentiality and integrity of those communications are effectively compromised once an attacker reaches the industrial LAN; availability is unaffected and no public exploit code has been identified at time of analysis, with no confirmed active exploitation. The practical barrier is the required adjacent-network position rather than any credential or user interaction, making this a moderately high priority OT/ICS exposure rather than an internet-reachable mass-exploitation issue.

RemediationAI

The supplied data does not identify a specific fixed firmware version, so the first action is to open Moxa's advisory MPSA-262560 (https://www.moxa.com/en/support/product-support/security-advisory/mpsa-262560-cve-2026-109812,-cve-2026-109813-vulnerabilities-in-industrial-computing-products) and apply the vendor's recommended firmware update for the AIG-302 Series as soon as it is published; because the key is compiled into /usr/bin/sysman rather than stored in a writable keystore, replacing the binary or firmware is the only way to retire the exposed key material, and any key rotation must come from Moxa rather than from local configuration. Until that update is applied, treat every AIG-302 Series unit as incapable of guaranteeing communication confidentiality or integrity and compensate at the network layer: place the devices on a dedicated, tightly segmented OT VLAN with no routing to corporate or internet-facing networks, and enforce that boundary with managed switch ACLs or an industrial firewall so that AV:A access is genuinely hard to obtain - the trade-off is reduced management flexibility and additional rules to maintain. Where the protected channel can be tunnelled, terminate it inside an IPsec or TLS gateway that uses locally managed, per-site keys, but note this adds latency, key-management overhead, and does not fix the underlying device-side key. If sysman-dependent services are not operationally required, disabling them removes the exposed interface entirely, at the cost of losing the management functionality they provide. Finally, monitor the OT segment for anomalous interception, replay, or traffic-manipulation patterns, since once an attacker recovers the key the device itself cannot detect the compromise.

Affected VersionsENISA

AIG-302 Series 1.0.0 ≤1.4.0

Affected Packages

euvd aig_302_series no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

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

Technical ContextAI · show details

This is a textbook instance of CWE-321 (Use of Hard-coded Cryptographic Key). The sysman utility, shipped at /usr/bin/sysman on Moxa AIG-302 Series industrial computers, carries private key material baked directly into the binary rather than into a per-device keystore or secure element. Because the same static key is present on every affected unit, it is not a secret in any meaningful sense: anyone with a copy of the firmware can extract it offline with standard reverse-engineering tooling and then apply it against any in-scope device. The affected product is identified by the CPE cpe:2.3:a:moxa:aig-302_series:*:*:*:*:*:*:*:*, with the wildcard version component indicating that the flaw is tied to the firmware generation rather than to a single release. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N) and the independent CVSS 3.1 assessment (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) agree on the core properties: adjacent network access is required, no privileges or user interaction are needed, and impact is confined to confidentiality and integrity of communications with no availability effect. The attack prerequisite is therefore twofold - a foothold on the same industrial network segment and possession of the recovered key - after which the attacker can passively decrypt or actively manipulate traffic that the device believes is protected.

Know when Aig 302 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 8.6 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 8.1 HIGH

Adjacent network access (AV:A) with no privileges or interaction (PR:N/UI:N); a static embedded key enables decryption and forgery giving C:H/I:H, with no availability impact (A:N).

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

Primary rating from Vendor (Moxa).

CVSS VectorVendor: Moxa

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

DescriptionCVE.org

A hard-coded cryptographic key vulnerability exists in the /usr/bin/sysman of some of Moxa's industrial computing products. An unauthenticated attacker with adjacent network access could exploit the exposed private key material to compromise the confidentiality and integrity of communications.

Executive ViewAI

Why It Matters

Moxa AIG-302 Series industrial computers contain a hard-coded cryptographic key that allows anyone with access to the same network segment to decrypt or tamper with device communications. This affects organizations relying on these devices in OT environments, where compromised data integrity could disrupt industrial processes or safety systems. With no vendor patch available, leadership should prioritize network segmentation and monitoring to reduce exposure until a fix is released.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: network segmentation to isolate affected devices on separate VLANs; strict firewall rules to limit access to trusted hosts; continuous monitoring for anomalous communications; disabling unnecessary services; implementing additional encryption at higher layers (e.g., TLS VPN) that does not use the compromised key; and physical security controls to prevent unauthorized local access.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Low
industrial IoT gateway, niche OT/ICS deployment footprint
Data Quality
5 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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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
Controlled
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Related Vulnerabilities in Moxa Industrial Computing Auth and Hardcoded Key Flaws

View all 2

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