Arbitrary process whitelisting via exposed driver IOCTL
Published Sep 8, 2026 · Updated Sep 9, 2026
Exposed IOCTL access control in ASUSTeK Computer Inc. Armoury Crate 6.5.7 and earlier allows local users to whitelist arbitrary process IDs. A crafted IOCTL request bypasses the driver's verification and causes it to accept an attacker-selected process identifier as trusted. Low-privileged local access is required; the demonstrated consequence is unauthorized whitelist modification, not code execution or data disclosure.
Summary
What happened
Exposed IOCTL access control in ASUSTeK Computer Inc. Armoury Crate 6.5.7 and earlier allows local users to whitelist arbitrary process IDs. A crafted IOCTL request bypasses the driver's verification and causes it to accept an attacker-selected process identifier as trusted. Low-privileged local access is required; the demonstrated consequence is unauthorized whitelist modification, not code execution or data disclosure.
The record
- CVE
- CVE-2026-16003
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- ASUSTeK Computer Inc.
- Product
- Armoury Crate
- Classifications
- CWE-782
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=6.5.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo