# CVE-2019-25764: Privilege escalation in AURA SYNC

> A local attacker can exploit insufficient access control in the ASUS AURA SYNC driver to invoke arbitrary IOCTLs and escalate privileges.

- **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:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-6jpp-g7h2-ch5p

## What is CVE-2019-25764?

CVE-2019-25764 is a high-severity vulnerability in ASUS AURA SYNC, published on 17 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

**UNSUPPORTED WHEN ASSIGNED**  Exposed IOCTL with Insufficient Access Control in the ASUS AURA SYNC driver allows a local user to bypass the driver's verification and invoke arbitrary IOCTLs, resulting in privilege escalation.

Refer to the 'End-of-Life Notice and Driver Update for Legacy ASUS Drivers ' section on the ASUS Security Advisory for more information.

Weakness: CWE-782 (Exposed IOCTL with Insufficient Access Control)

## Which versions are affected by CVE-2019-25764?


## How do I fix CVE-2019-25764?

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

## Is CVE-2019-25764 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25764 and fix it if it is affected.

What it is: CVE-2019-25764 is a high-severity vulnerability in ASUS AURA SYNC, published on 17 Jul 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-2019-25764 in the wild and no public exploit code.

Affected product: ASUS AURA SYNC. 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-2019-25764/ (Markdown: https://insights.sbomify.com/CVE-2019-25764/index.md)
```

## Sources

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

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