CVE-2026-16006

MEDIUMPre-NVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.7Exploit: None knownExposed: 0

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

Exposure of Sensitive System Information to an Unauthorized Control Sphere in Armoury Crate driver allows a local user to obtain kernel virtual addresses via a crafted IOCTL request by bypassing the driver's verification, potentially providing further insight into the kernel memory layout.Refer to the ' Security Update for Armoury Crate App  ' section on the ASUS Security Advisory for more information.

CVSS v3
5.7
EG Score
5.7(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity57% × 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

Advisory Details (1)

Auto-updated Sep 8, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

ASUS Security Advisory | Latest Vulnerability Update

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

Vendor Advisories for CVE-2026-16006(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 16× in last 7d / 32× 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-19 14:05 UTCGHSA enrichment
  2. 2026-09-18 11:49 UTCEG score recompute
  3. 2026-09-18 11:49 UTCGHSA enrichment
  4. 2026-09-17 09:32 UTCEG score recompute
  5. 2026-09-17 09:32 UTCGHSA enrichment
  6. 2026-09-17 08:49 UTCEG score recompute
  7. 2026-09-17 08:49 UTCGHSA enrichment
  8. 2026-09-17 02:58 UTCEG score recompute
  9. 2026-09-17 02:58 UTCGHSA enrichment
  10. 2026-09-16 14:07 UTCEPSS rescore
  11. 2026-09-16 00:05 UTCEG score recompute
  12. 2026-09-16 00:05 UTCGHSA enrichment
  13. 2026-09-14 21:48 UTCGHSA enrichment
  14. 2026-09-13 19:31 UTCGHSA enrichment
  15. 2026-09-12 17:14 UTCEG score recompute
  16. 2026-09-12 17:14 UTCGHSA enrichment
  17. 2026-09-12 15:00 UTCEPSS rescore
  18. 2026-09-11 14:57 UTCEG score recompute
  19. 2026-09-11 14:57 UTCGHSA enrichment
  20. 2026-09-11 14:52 UTCEPSS rescore
  21. 2026-09-11 09:36 UTCEPSS rescore
  22. 2026-09-10 12:40 UTCEG score recompute
  23. 2026-09-10 12:40 UTCGHSA enrichment
  24. 2026-09-10 09:34 UTCEPSS rescore
  25. 2026-09-09 10:23 UTCEG score recompute
Show 7 more
  1. 2026-09-09 10:23 UTCGHSA enrichment
  2. 2026-09-08 22:00 UTCEPSS rescore
  3. 2026-09-08 14:10 UTCGHSA enrichment
  4. 2026-09-08 03:34 UTCEG score recompute
  5. 2026-09-08 03:34 UTCGHSA enrichment
  6. 2026-09-08 02:30 UTCEG score recompute
  7. 2026-09-08 02:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16006?
CVE-2026-16006 is a medium vulnerability published on September 8, 2026. Exposure of Sensitive System Information to an Unauthorized Control Sphere in Armoury Crate driver allows a local user to obtain kernel virtual addresses via a crafted IOCTL request by bypassing the driver's verification, potentially providing further insight into the kernel memory layout.Refer to…
When was CVE-2026-16006 disclosed?
CVE-2026-16006 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-16006 actively exploited?
CVE-2026-16006 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-16006?
CVE-2026-16006 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-16006?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16006, 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-16006

Explore →

Is Your Infrastructure Affected by CVE-2026-16006?

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

Start Free Scan →Browse All CVEs