How severe is CVE-2026-16003?

CVE-2026-16003 has a CVSS 4.0 base score of 2.0, rated low severity.

Is CVE-2026-16003 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-16003?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-16003 published?

CVE-2026-16003 was published on 2026-09-08 and last updated on 2026-09-17.

CVE-2026-16003

CVE-2026-16003 is a low-severity vulnerability with a CVSS 4.0 base score of 2.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-782.

Key facts

Severity: Low (CVSS 4.0 base score 2.0)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-782
Published: 2026-09-08
Last modified: 2026-09-17

Description

Exposed IOCTL with Insufficient Access Control in Armoury Crate driver allows a local user to add an arbitrary process identifier to the driver's whitelist via a crafted IOCTL request by bypassing the driver's verification.Refer to the ' Security Update for Armoury Crate App ' section on the ASUS Security Advisory for more information.

Frequently asked questions

What is CVE-2026-16003?: Exposed IOCTL with Insufficient Access Control in Armoury Crate driver allows a local user to add an arbitrary process identifier to the driver's whitelist via a crafted IOCTL request by bypassing the driver's verification.Refer to the ' Security Update for Armoury Crate App ' section on the ASUS Security Advisory for more information.
How severe is CVE-2026-16003?: CVE-2026-16003 has a CVSS 4.0 base score of 2.0, rated low severity.
Is CVE-2026-16003 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-16003?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-16003 published?: CVE-2026-16003 was published on 2026-09-08 and last updated on 2026-09-17.

References

https://www.asus.com/security-advisory

Other CWE-782 vulnerabilities

CVE-2024-39251 — Critical (CVSS 10.0): An issue in the component ControlCenter.sys/ControlCenter64.sys of ThundeRobot Control Center v2.0.0.10 allows…
CVE-2024-4196 — Critical (CVSS 10.0): An improper input validation vulnerability was discovered in Avaya IP Office that could allow remote command or code…
CVE-2024-32370 — Critical (CVSS 9.8): An issue in HSC Cybersecurity HC Mailinspector 5.2.17-3 through 5.2.18 allows a remote attacker to obtain sensitive…
CVE-2024-30804 — Critical (CVSS 9.8): An issue discovered in the DeviceIoControl component in ASUS Fan_Xpert before v.10013 allows an attacker to execute…
CVE-2026-84408 — High (CVSS 8.8): QND contains an improper access control vulnerability in a named pipe, which may allow a local attacker who is logged…
CVE-2024-33220 — High (CVSS 8.8): An issue in the component AslO3_64.sys of ASUSTeK Computer Inc AISuite3 v3.03.36 3.03.36 allows attackers to escalate…

Browse all CWE-782 vulnerabilities →