# CVE-2026-8917: Memory corruption in AI Suite3

> A local attacker can exploit an untrusted pointer dereference in ASUS GPU Tweak utilities to write to arbitrary memory, leading to privilege escalation.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-cc5p-f4h4-cfmj

## What is CVE-2026-8917?

CVE-2026-8917 is a high-severity memory corruption vulnerability in ASUS AI Suite3, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted Pointer Dereference in ASUS GPU Tweak III, GPUTweakII, AI Suite3, and VGAdll: An IOCTL vulnerability allows a local attacker to write a specific value to an arbitrary memory address, potentially leading to privilege escalation.
Refer to the ' 
Security Update for ASUS GPU Tweak III, GPU Tweak II, AI Suite 3, and Armoury Crate Security Bulletin   ' section on the ASUS Security Advisory for more information.

Weakness: CWE-822 (Untrusted Pointer Dereference)

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


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

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

## Is CVE-2026-8917 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8917 is a high-severity memory corruption vulnerability in ASUS AI Suite3, published on 11 Aug 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-8917 in the wild and no public exploit code.

Affected product: ASUS AI Suite3. 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-8917/ (Markdown: https://insights.sbomify.com/CVE-2026-8917/index.md)
```

## Sources

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

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