Overview

On 20 October 2026 CISA published advisory ICSA-26-293-03 (Revision 1) covering the Moxa AIG-302 running ThingsPro Edge firmware version 1.4.0 and earlier. The AIG-302 is an edge computing gateway of the kind used to collect field data and relay it northbound. CISA lists the affected sectors as Critical Manufacturing, Energy, and Water and Wastewater Systems, deployed worldwide, with Moxa headquartered in Taiwan.

The advisory describes two vulnerabilities, both reachable only from an adjacent network. Both were reported to CISA by Ievgen Bondarenko. The fix is ThingsPro Edge v1.4.1, and CISA refers readers to Moxa’s own bulletin, MPSA-262560.

Source note: this article is based on the CISA advisory page only. We did not open Moxa’s MPSA-262560 or the NVD entries, so details beyond the CISA text are not independently confirmed.

The two vulnerabilities

CVECWECVSS v3.1CVSS v4.0
CVE-2026-109813CWE-321, hard-coded cryptographic key8.1 High8.6 High
CVE-2026-109812CWE-862, missing authorization6.8 Medium6.9 Medium

CVE-2026-109813: hard-coded private key in /usr/bin/sysman

CISA describes a private key embedded in the /usr/bin/sysman binary. An unauthenticated attacker with adjacent network access could use the exposed key to compromise the confidentiality and integrity of communications. The published vectors are:

  • CVSS v3.1: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • CVSS v4.0: 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

No privileges, no user interaction and low complexity are required; the only gate is network adjacency. The advisory does not say which protocol or service uses the key, and we have not seen that detail in a source we opened. Because the same key material would ship in every unit running an affected build, anyone who obtains the firmware could in principle hold it. That inference is ours, not CISA’s.

CVE-2026-109812: missing authorization on /api/v1/secrets/

An internal API endpoint, /api/v1/secrets/, lacks an authorization check. A privileged, authenticated attacker with adjacent network access could reach sensitive data, potentially including cryptographic key material. The scope is changed in the v3.1 vector (S:C), reflecting impact beyond the vulnerable component:

  • CVSS v3.1: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
  • CVSS v4.0: CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Why this matters in a Purdue-model deployment

Edge gateways typically straddle levels: they speak to field devices below and to historians, brokers or cloud services above. Adjacent-network access therefore means different things by site. On a flat plant network, any compromised workstation or rogue laptop is adjacent. On a segmented design, adjacency is limited to the gateway’s own VLAN or cell zone.

The two flaws also chain conceptually. A secrets endpoint that discloses key material is more dangerous when the gateway’s communications are already protectable with a key an attacker can obtain. Whether the two can actually be chained on a real device is not stated by CISA; treat that as our analysis, not a finding.

Exploitation status

CISA states that no known public exploitation of these vulnerabilities has been reported to it, and that they are not exploitable remotely. We found no evidence of exploitation as of 2026-10-27 in the CISA advisory (the only source we opened for this issue). The advisory page does not include SSVC data.

Remediation

From the CISA advisory (vendor guidance):

  1. Upgrade ThingsPro Edge to v1.4.1.
  2. If the device has Internet access, use the web console’s Software Upgrades page to check for and install the update.
  3. Otherwise, download the v1.4.1 patch from Moxa’s product website or Software Release Service and upload it through the web console’s Package Upload option.
  4. Consult Moxa’s advisory MPSA-262560.
  5. CISA’s general guidance: keep control system devices off the Internet, place them behind firewalls isolated from business networks, and use up-to-date VPNs for remote access.

Our additional suggestions, not from CISA or Moxa:

  • Inventory AIG-302 units and confirm the running ThingsPro Edge version; anything at 1.4.0 or earlier is in scope.
  • Restrict Layer 2 reachability to the gateway’s management and service ports to a small set of jump hosts or engineering stations.
  • After patching, consider whether secrets or keys stored on the device should be rotated. Moxa’s text, as relayed by CISA, does not say whether the fix invalidates previously exposed material, so confirm with the vendor.
  • Monitor for unexpected hosts on the gateway’s segment, since adjacency is the prerequisite for both issues.

Takeaway

Neither issue is remotely exploitable and neither is reported as exploited, so this is a scheduled-patch item rather than an emergency. The hard-coded key is the more serious of the two, with an 8.1 score and no authentication requirement, and the right prioritisation depends on how well the gateway’s network segment is controlled.

Sources

Tags
MoxaAIG-302ThingsPro Edgeedge gatewayhard-coded keyCWE-321CWE-862ICSA-26-293-03