Moxa AIG-302 ThingsPro Edge through 1.4.0 can leak keys
An unauthenticated adjacent attacker can abuse a hard-coded key; a logged-in user can read the secrets API.
Hard-coded key in Moxa sysman (adjacent network)
A hard-coded cryptographic key in /usr/bin/sysman on some Moxa industrial computing products exposes private key material. An unauthenticated attacker on an adjacent network can use it to break the confidentiality and integrity of communications. Availability is not affected. Moxa has not listed specific builds or fixed versions.
What to do: Apply Moxa's update for CVE-2026-109813. No workaround is stated.
| Product | Affected |
|---|---|
| Moxa industrial computing products (/usr/bin/sysman) | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
An unauthenticated adjacent attacker can abuse a hard-coded key; a logged-in user can read the secrets API.
Canada's Cyber Centre warns Moxa AIG-302 versions through 1.4.1 have two newly listed vulnerabilities.
Today 2.2K readers · 2.8K views · 404 reads · all time 108K views