# CVE-2026-8921: Path traversal in ASUS Business Manager

> A local attacker can execute arbitrary code with SYSTEM privileges by tampering with IPC messages in ASUS Business Manager.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/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:** 3 Jul 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-2844-p28c-wcj6

## What is CVE-2026-8921?

CVE-2026-8921 is a high-severity path traversal vulnerability in ASUS Business Manager, published on 3 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

External Control of File Name or Path vulnerability in ASUS Business Manager allows a local user to execute arbitrary code with SYSTEM privileges via a tampered IPC message.
Refer to the '
Security Update for ASUS Business Manager ' section on the ASUS Security Advisory for more information.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-8921 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8921 is a high-severity path traversal vulnerability in ASUS Business Manager, published on 3 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-2026-8921 in the wild and no public exploit code.

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

## Sources

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

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