# CVE-2026-1880: Race condition in DriverHub

> A local attacker can exploit a race condition in ASUS DriverHub to modify update resources and execute arbitrary code with elevated privileges.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Apr 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-vmw6-xgxq-pw9v

## What is CVE-2026-1880?

CVE-2026-1880 is a medium-severity vulnerability in ASUS DriverHub, published on 16 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An Incorrect Permission Assignment for Critical Resource vulnerability in the ASUS DriverHub update process allows privilege escalation due to improper protection of required execution resources during the validation phase, permitting a local user to make unprivileged modifications. This allows the altered resource to pass system checks and be executed with elevated privileges upon a user-initiated update.
Refer to the 'Security Update for ASUS DriverHub' section on the ASUS Security Advisory for more information.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2026-1880 being exploited?

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

Public exploit code:

- ASUS DriverHub Driver Update Process TOCTOU Vulnerability Leading to LPE (github_poc): https://github.com/seokjohn/CVE-2026-1880

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1880 is a medium-severity vulnerability in ASUS DriverHub, published on 16 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-1880 in the wild and no public exploit code.

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

## Sources

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

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