# CVE-2026-16004: ASUS Armoury Crate driver insufficient access control in IOCTL

Source: https://junglewise.ai/threats/cve-2026-16004-asus-armoury-crate-driver-insufficient-access-control-in-ioctl  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-08. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-16004 · Severity: info · Published 2026-09-08

The Armoury Crate driver on ASUS systems contains a flaw that allows local users to read and write arbitrary PCI/PCIe configuration space without proper authorization checks. This could allow a local attacker to modify hardware settings or extract sensitive information, potentially compromising system stability or enabling further attacks.

Technologies: [ASUS Armoury Crate](https://junglewise.ai/threats/technologies/armoury-crate). Vendors: [ASUS](https://junglewise.ai/threats/vendors/asus).

## Quick answers

**Is CVE-2026-16004 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-16004 being exploited in the wild.

**How severe is CVE-2026-16004?** Informational severity, published 8 September 2026.

**Which products and versions are affected?** ASUS Armoury Crate.

**Is there a fix for CVE-2026-16004?** 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-16004 attacked?** It is attacked with local access.

**Am I affected by CVE-2026-16004?** Check whether you run ASUS Armoury Crate. 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

The vulnerability is an insufficient access control issue in an IOCTL handler within the ASUS Armoury Crate driver. An attacker with local system access can craft malicious IOCTL requests that bypass the driver's verification mechanisms to directly read and write PCI/PCIe configuration space. This requires local code execution privileges but no authentication. The flaw allows unauthorized hardware-level configuration access, which could be leveraged for privilege escalation, hardware tampering, or information disclosure. A security update is available via the ASUS Security Advisory.

## Affected products

- ASUS Armoury Crate

## Timeline

- 2026-09-08: disclosed

## References

- [https://www.asus.com/security-advisory](https://www.asus.com/security-advisory)

## Related threats

- [ASUS Armoury Crate missing authorization in inter-process interface](https://junglewise.ai/threats/cve-2026-110464-missing-authorization-in-asus-armoury-crate-allows-a-local)
- [ASUS Armoury Crate uncontrolled search path DLL injection](https://junglewise.ai/threats/cve-2026-102438-an-uncontrolled-search-path-element-vulnerability-in-asus)
- [ASUS Armoury Crate privilege escalation via driver authentication bypass](https://junglewise.ai/threats/cve-2026-75811-asus-armoury-crate-privilege-escalation-via-driver-authentication)
- [ASUS Armoury Crate exposed dangerous method denial of service](https://junglewise.ai/threats/cve-2026-75810-asus-armoury-crate-exposed-dangerous-method-denial-of-service)
- [ASUS Armoury Crate privilege escalation via insufficient IOCTL access control](https://junglewise.ai/threats/cve-2026-75809-asus-armoury-crate-privilege-escalation-via-insufficient-ioctl)