Quick answers
- Is CVE-2026-109813 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109813 being exploited in the wild.
- How severe is CVE-2026-109813?
- Informational severity, published 16 October 2026.
- Which products and versions are affected?
- Moxa Industrial Computing Products <UNKNOWN>.
- Is there a fix for CVE-2026-109813?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-109813 attacked?
- It is attacked from the adjacent network or over the network, in a network appliance.
- Am I affected by CVE-2026-109813?
- Check whether you run Moxa Industrial Computing Products at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A hard-coded root CA private key is embedded in the `/usr/bin/sysman` binary in affected Moxa industrial computing products, enabling unauthenticated attackers with adjacent network access to decrypt and forge cryptographic material. The vulnerability allows compromise of both confidentiality and integrity of communications without requiring authentication or user interaction. An attacker can use the exposed private key material to perform man-in-the-middle attacks, impersonate the system, or forge certificates.
Affected products
- Moxa Industrial Computing Products <UNKNOWN>
Timeline
- 2026-10-16: advisory