cve.bz

CVE-2026-109813 moxa aig-302 series: Use of Hard-coded Cryptographic Key

8.6 highEPSS 0.2%

High (8.6) in moxa aig-302 series. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

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
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-321 Use of Hard-coded Cryptographic Key
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-109813 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109813?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109813?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109813 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-109813

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-109813](https://cve.bz/cve/badge/CVE-2026-109813.svg)](https://cve.bz/cve/CVE-2026-109813)

HTML:

<a href="https://cve.bz/cve/CVE-2026-109813"><img src="https://cve.bz/cve/badge/CVE-2026-109813.svg" alt="CVE-2026-109813"></a>

Affected

  • moxa:aig-302 series

Versions

From the CNA's record in the CVE List.

ProductAffected
Moxa AIG-302 Seriesfrom 1.0.0 through 1.4.0

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-293-03Moxa AIG-302 ThingsPro Edge2026-10-20Critical Manufacturing, Energy, Water and Wastewater SystemsMoxa Moxa AIG-302 ThingsPro Edge firmware: <=1.4.0none listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

References

Check your stackJSON