Improper Restriction of Software Interfaces to Hardware Features in ASUS Armoury Crate allows a local user to modify hardware configuration settings and potentially cause hardware damage by bypassing driver authentication and accessing critical model-specific registers.Refer to the ' Security Update for Armoury Crate App' section on the ASUS Security Advisory for more information.
CVE-2026-75811
This medium-severity CVE scores 5.8 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(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 computedSeverity58% × 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, 2026ASUS Security Advisory | Latest Vulnerability Update
https://www.asus.com/security-advisoryVendor Advisories for CVE-2026-75811(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 15× in last 7d / 33× 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.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 11:52 UTCEG score recompute
- 2026-09-18 11:52 UTCGHSA enrichment
- 2026-09-17 09:32 UTCEG score recompute
- 2026-09-17 09:32 UTCGHSA enrichment
- 2026-09-17 08:59 UTCEG score recompute
- 2026-09-17 08:59 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 06:56 UTCGHSA enrichment
- 2026-09-15 04:36 UTCEG score recompute
- 2026-09-15 04:36 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 02:16 UTCEG score recompute
- 2026-09-14 02:16 UTCGHSA enrichment
- 2026-09-12 23:56 UTCGHSA enrichment
- 2026-09-11 21:36 UTCEG score recompute
- 2026-09-11 21:36 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 19:15 UTCEG score recompute
- 2026-09-10 19:15 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 16:55 UTCEG score recompute
- 2026-09-09 16:55 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 14:10 UTCGHSA enrichment
Show 8 moreShow fewer
- 2026-09-08 13:44 UTCEG score recompute
- 2026-09-08 13:43 UTCGHSA enrichment
- 2026-09-08 13:07 UTCEG score recompute
- 2026-09-08 13:06 UTCGHSA enrichment
- 2026-09-08 03:34 UTCEG score recompute
- 2026-09-08 03:34 UTCGHSA enrichment
- 2026-09-08 02:30 UTCEG score recompute
- 2026-09-08 02:29 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-75811?
When was CVE-2026-75811 disclosed?
Is CVE-2026-75811 actively exploited?
What is the CVSS score of CVE-2026-75811?
How do I remediate CVE-2026-75811?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75811
Is Your Infrastructure Affected by CVE-2026-75811?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.