# CVE-2025-57227: Privilege escalation in n/a

> Attackers can escalate privileges by placing a crafted executable in a parent folder due to an unquoted service path in Kingo ROOT.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-r9fw-cwjr-j3hp

## What is CVE-2025-57227?

CVE-2025-57227 is a high-severity vulnerability in n/a, published on 29 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An unquoted service path in Kingosoft Technology Ltd Kingo ROOT v1.5.8.3353 allows attackers to escalate privileges via placing a crafted executable file into a parent folder.

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

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


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

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

## Is CVE-2025-57227 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57227 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57227 is a high-severity vulnerability in n/a, published on 29 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57227 exists.

Affected product: n/a. 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-57227/ (Markdown: https://insights.sbomify.com/CVE-2025-57227/index.md)
```

## Sources

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

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