# CVE-2019-25293: Blue Stacks App Player 2.4.44.62.57 - "BstHdLogRotatorSvc" Unquote Service Path

> Local attackers can escalate privileges and execute arbitrary code by exploiting an unquoted service path in BlueStacks App Player.

- **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:** 6 Feb 2026
- **Updated:** 17 Jun 2026

## What is CVE-2019-25293?

CVE-2019-25293 is a high-severity vulnerability in bluestacks Blue Stacks App Player, published on 6 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BlueStacks App Player 2.4.44.62.57 contains an unquoted service path vulnerability in the BstHdLogRotatorSvc service that allows local attackers to potentially execute arbitrary code. Attackers can exploit the unquoted path in C:\Program Files (x86)\Bluestacks\HD-LogRotatorService.exe to inject malicious executables and escalate privileges.

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

## Which versions are affected by CVE-2019-25293?


## How do I fix CVE-2019-25293?

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

## Is CVE-2019-25293 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25293 and fix it if it is affected.

What it is: CVE-2019-25293 is a high-severity vulnerability in bluestacks Blue Stacks App Player, published on 6 Feb 2026. 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-2019-25293 exists.

Affected product: bluestacks Blue Stacks App Player. 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-2019-25293/ (Markdown: https://insights.sbomify.com/CVE-2019-25293/index.md)
```

## Sources

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

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