# CVE-2026-8070: Privilege escalation in Armoury Crate

> Local attackers can bypass driver validation to read and write physical memory, enabling privilege escalation in ASUS Armoury Crate.

- **Severity:** High 7.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-cgxr-jgj8-7wp2

## What is CVE-2026-8070?

CVE-2026-8070 is a high-severity vulnerability in ASUS Armoury Crate, published on 29 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2026-8070?


## How do I fix CVE-2026-8070?

No fix has been published for CVE-2026-8070 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8070 being exploited?

There is no known exploitation of CVE-2026-8070 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8070 and fix it if it is affected.

What it is: CVE-2026-8070 is a high-severity vulnerability in ASUS Armoury Crate, published on 29 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8070 in the wild and no public exploit code.

Affected product: ASUS Armoury Crate. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8070/ (Markdown: https://insights.sbomify.com/CVE-2026-8070/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8070
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8070
- OSV: https://osv.dev/vulnerability/CVE-2026-8070

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8070/
Summaries are generated and may contain mistakes; the official description above is the record.