Is CVE-2026-4483 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-4483 being exploited in the wild.

How severe is CVE-2026-4483?

Informational severity, with a CVSS score of 7, published 8 April 2026.

Which products and versions are affected?

Moxa MxGeneralIo Windows 7: before v1.4.0; Windows 10: before v1.5.0; Windows 11: before v1.5.0.

Is there a fix for CVE-2026-4483?

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-4483 attacked?

It is attacked over the network, in an operating system.

Am I affected by CVE-2026-4483?

Check whether you run Moxa MxGeneralIo 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.

CVE-2026-4483: Moxa MxGeneralIo insufficient access control in IOCTL

CVE-2026-4483 · Severity: info · CVSS 7 · Published 2026-04-08

A security vulnerability exists in the MxGeneralIo utility used by Moxa industrial x86 computers, which are typically used in manufacturing, power, and transportation sectors. An attacker with high-level access could exploit this flaw to gain even higher system privileges or cause the computer to crash. This could lead to unauthorized control over the device or a complete service outage, potentially disrupting industrial operations.

Vendors: Moxa.

Quick answers

Is CVE-2026-4483 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-4483 being exploited in the wild.
How severe is CVE-2026-4483?: Informational severity, with a CVSS score of 7, published 8 April 2026.
Which products and versions are affected?: Moxa MxGeneralIo Windows 7: before v1.4.0; Windows 10: before v1.5.0; Windows 11: before v1.5.0.
Is there a fix for CVE-2026-4483?: 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-4483 attacked?: It is attacked over the network, in an operating system.
Am I affected by CVE-2026-4483?: Check whether you run Moxa MxGeneralIo 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

An exposed IOCTL (Input/Output Control) vulnerability (CWE-782) exists in the MxGeneralIo utility for Moxa industrial x86 computers. The utility fails to implement sufficient access controls on IOCTL methods that permit direct read and write access to Model-Specific Registers (MSR) and system memory. While the CVSS vector indicates a network attack vector, the advisory text specifies a local attacker with high privileges is required. Successful exploitation on Windows 7 systems can lead to privilege escalation, while on Windows 10 and 11 systems, it typically results in a Blue Screen of Death (BSoD), causing a denial-of-service condition. Moxa has released patches (v1.4.0 for Windows 7 and v1.5.0 for Windows 10/11) to address the issue.

Affected products

Moxa MxGeneralIo Windows 7: before v1.4.0; Windows 10: before v1.5.0; Windows 11: before v1.5.0

Timeline

2026-04-08: disclosed
2026-04-08: advisory

References

https://www.moxa.com/en/support/product-support/security-advisory/mpsa-254811-cve-2026-4483-exposed-ioctl-with-insufficient-access-control-vulnerability-in-the-utility-for-x86-computers

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.