CVE-2026-8070
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect permission assignment for a critical resource in Armoury Crate allows a local user to bypass the driver’s validation mechanism, resulting in unauthorized read and write access to physical memory.Refer to the ' Security Update for Armoury Crate App ' section on the ASUS Security Advisory for more information.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceArmoury Crate contains an incorrect permission assignment that allows a local user to bypass the driver's validation mechanism, granting unauthorized read and write access to physical memory. This is a privilege escalation and memory corruption vulnerability in the ASUS Armoury Crate software and its associated kernel driver.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Armoury Crate is installedCheck for the presence of Armoury Crate in the system: Open Programs and Features (appwiz.cpl) and look for 'Armoury Crate', or check the default install path at C:\Program Files\ASUS\Armoury Crate\Affected if Armoury Crate is installed on the system
-
Identify installed Armoury Crate versionIn Programs and Features, locate Armoury Crate and note the version number displayed. Compare this version against the latest ASUS security update to determine if it includes the CVE-2026-8070 patch.Affected if The installed version is older than the patched version released for CVE-2026-8070
-
Locate and inspect ASUS driver componentsSearch for ASUS driver files in the system: Check C:\Windows\System32\drivers\ for files starting with 'Aura' or 'Armoury' (e.g., Aura.sys, ArmouryCrateDriver.sys), and check C:\Program Files\ASUS\Armoury Crate\ for driver-related files.Affected if ASUS driver files exist in system directories without proper driver signing or with improper permissions
-
Check driver file permissionsRight-click on the identified ASUS driver files, go to Properties > Security tab, and review the permissions. Specifically check if non-admin users have Write or Full Control permissions to these driver files.Affected if Non-privileged users have Write or Full Control access to ASUS driver files in system directories
The system is affected if Armoury Crate is installed with an unpatched version and ASUS driver files are present with permissive access controls that allow non-admin users to modify them.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the ASUS security update for Armoury Crate immediately. If a patch is not yet available, consider disabling or removing Armoury Crate until the update is released, as the vulnerability allows physical memory access.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8070 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data