# CVE-2026-109813: Shared Hard-coded Root CA Private Key

> An attacker with adjacent network access can exploit a hard-coded root CA private key to compromise the confidentiality and integrity of communications in Moxa industrial devices.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-4w88-hm3w-rh83

## What is CVE-2026-109813?

CVE-2026-109813 is a high-severity vulnerability in Moxa AIG-302 Series, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-109813?


## How do I fix CVE-2026-109813?

No fix has been published for CVE-2026-109813 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109813 being exploited?

There is no known exploitation of CVE-2026-109813 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109813 and fix it if it is affected.

What it is: CVE-2026-109813 is a high-severity vulnerability in Moxa AIG-302 Series, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109813 in the wild and no public exploit code.

Affected product: Moxa AIG-302 Series. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109813/ (Markdown: https://insights.sbomify.com/CVE-2026-109813/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109813
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109813
- OSV: https://osv.dev/vulnerability/CVE-2026-109813

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109813/
Summaries are generated and may contain mistakes; the official description above is the record.