# CVE-2026-7480: Privilege escalation in ASUS System Control Interface

> A local attacker can elevate privileges to SYSTEM and execute arbitrary code via a crafted RPC call in ASUS System Control Interface.

- **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:** 29 May 2026
- **Also known as:** GHSA-9p3q-hww2-4c52

## What is CVE-2026-7480?

CVE-2026-7480 is a high-severity vulnerability in ASUS System Control Interface, 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

An Incorrect Permission Assignment for Critical Resource vulnerability in ASUS System Control Interface allows a local user to elevate privileges to SYSTEM and execute arbitrary code via a crafted RPC call that bypass the validation mechanism.
Refer to the 'Security Update for ASUS System Control Interface' 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-7480?


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

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

## Is CVE-2026-7480 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7480 is a high-severity vulnerability in ASUS System Control Interface, 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-7480 in the wild and no public exploit code.

Affected product: ASUS System Control Interface. 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-7480/ (Markdown: https://insights.sbomify.com/CVE-2026-7480/index.md)
```

## Sources

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

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