# CVE-2025-8070: Windows service registered with an unquoted ImagePath vulnerability in the system registry

> Local attackers can escalate privileges to SYSTEM by exploiting unquoted service paths in ASUSTOR ABP and AES software.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/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:** 23 Jul 2025
- **Updated:** 23 Jul 2025
- **Also known as:** GHSA-6q9j-6jj7-h2cx

## What is CVE-2025-8070?

CVE-2025-8070 is a critical vulnerability in ASUSTOR ABP and AES, published on 23 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Windows service configuration of ABP and AES contains an unquoted ImagePath registry value vulnerability. This allows a local attacker to execute arbitrary code by placing a malicious executable in a predictable location such as C:\Program.exe. If the service runs with elevated privileges, exploitation results in privilege escalation to SYSTEM level. This vulnerability arises from an unquoted service path affecting systems where the executable resides in a path containing spaces.
Affected products and versions include: ABP 2.0.7.6130 and earlier as well as AES 1.0.6.6133 and earlier.

Weakness: CWE-428 (Unquoted Search Path or Element)

## Which versions are affected by CVE-2025-8070?


## How do I fix CVE-2025-8070?

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

## Is CVE-2025-8070 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8070 and fix it if it is affected.

What it is: CVE-2025-8070 is a critical vulnerability in ASUSTOR ABP and AES, published on 23 Jul 2025. 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-2025-8070 in the wild and no public exploit code.

Affected product: ASUSTOR ABP and AES. 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-2025-8070/ (Markdown: https://insights.sbomify.com/CVE-2025-8070/index.md)
```

## Sources

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

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