CVE-2026-16003

LOWPre-NVD 2.02.0—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
2.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
2.0
EG Score
2.0(medium)
EG Risk
9(Track)
EG Risk 9/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity20% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 17, 2026

References (1)

Vendor Advisories for CVE-2026-16003(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 09:32 UTCEG score recompute
  3. 2026-09-17 09:32 UTCGHSA enrichment
  4. 2026-09-17 08:49 UTCEG score recompute
  5. 2026-09-17 08:49 UTCGHSA enrichment
  6. 2026-09-16 14:07 UTCEPSS rescore
  7. 2026-09-16 05:14 UTCEPSS rescore
  8. 2026-09-15 01:06 UTCEG score recompute
  9. 2026-09-15 01:06 UTCGHSA enrichment
  10. 2026-09-13 16:46 UTCEPSS rescore
  11. 2026-09-12 06:16 UTCEG score recompute
  12. 2026-09-12 06:16 UTCGHSA enrichment
  13. 2026-09-11 14:52 UTCEPSS rescore
  14. 2026-09-11 09:36 UTCEPSS rescore
  15. 2026-09-10 09:34 UTCEPSS rescore
  16. 2026-09-09 11:25 UTCEG score recompute
  17. 2026-09-09 11:25 UTCGHSA enrichment
  18. 2026-09-09 10:30 UTCEG score recompute
  19. 2026-09-09 10:30 UTCGHSA enrichment
  20. 2026-09-08 22:00 UTCEPSS rescore
  21. 2026-09-08 14:10 UTCGHSA enrichment
  22. 2026-09-08 03:34 UTCEG score recompute
  23. 2026-09-08 03:34 UTCGHSA enrichment
  24. 2026-09-08 02:30 UTCEG score recompute
  25. 2026-09-08 02:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16003?
CVE-2026-16003 is a low vulnerability published on September 8, 2026. 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…
When was CVE-2026-16003 disclosed?
CVE-2026-16003 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16003 actively exploited?
CVE-2026-16003 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-16003?
CVE-2026-16003 has a CVSS v3 base score of 2.0 (NVD).
How do I remediate CVE-2026-16003?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16003, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16003

Explore →

Is Your Infrastructure Affected by CVE-2026-16003?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs