# CVE-2026-4483: Privilege escalation in MxGeneralIo

> A local attacker with high privileges can exploit exposed IOCTLs in MxGeneralIo to escalate privileges or cause a system crash.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9fq9-vh4p-342c

## What is CVE-2026-4483?

CVE-2026-4483 is a high-severity vulnerability in Moxa MxGeneralIo, published on 8 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An exposed IOCTL with an  insufficient access control vulnerability has been identified in the utility, MxGeneralIo, for Moxa’s industrial x86 computers. The affected utility, MxGeneralIo, exposes IOCTL methods that permit direct read and write access to MSR and system memory. A local attacker with high privileges could abuse these interfaces to perform unauthorized operations. Successful exploitation may result in privilege escalation on Windows 7 systems or cause a system crash (BSoD) on Windows 10 and 11 systems, leading to a denial-of-service condition. The vulnerability could slightly affect the confidentiality and integrity of the device, but availability might be heavily impacted. No impact to the subsequent system has been identified.

Weakness: CWE-782 (Exposed IOCTL with Insufficient Access Control)

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


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

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

## Is CVE-2026-4483 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4483 is a high-severity vulnerability in Moxa MxGeneralIo, published on 8 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4483 in the wild and no public exploit code.

Affected product: Moxa MxGeneralIo. 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-4483/ (Markdown: https://insights.sbomify.com/CVE-2026-4483/index.md)
```

## Sources

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

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