Moxa MxGeneralIo up to 1.3.x/1.4.x on Moxa exposed ioctl with insufficient access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Moxa MxGeneralIo up to 1.3.x/1.4.x on Moxa. It has been rated as problematic. This issue affects some unknown processing. This manipulation causes exposed ioctl with insufficient access control. This vulnerability is handled as CVE-2026-4483. It is possible to launch the attack on the local host. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in Moxa MxGeneralIo up to 1.3.x/1.4.x on Moxa. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a exposed ioctl with insufficient access control vulnerability. The CWE definition for the vulnerability is CWE-782. The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was released by Jason Huang. The advisory is shared at moxa.com. This vulnerability is known as CVE-2026-4483 since 03/20/2026. The exploitation appears to be easy. An attack has to be approached locally. The exploitation needs additional levels of successful authentication. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.4.0 or 1.5.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.moxa.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.0
VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Exposed ioctl with insufficient access controlCWE: CWE-782
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: MxGeneralIo 1.4.0/1.5.0
Timeline
03/20/2026 CVE reserved04/08/2026 Advisory disclosed
04/08/2026 VulDB entry created
04/08/2026 VulDB entry last update
Sources
Vendor: moxa.comAdvisory: moxa.com
Researcher: Jason Huang
Status: Confirmed
CVE: CVE-2026-4483 (🔒)
GCVE (CVE): GCVE-0-2026-4483
GCVE (VulDB): GCVE-100-356041
Entry
Created: 04/08/2026 10:36Changes: 04/08/2026 10:36 (68)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.