# CVE-2025-44964: Weak cryptography in n/a

> Attackers can intercept sensitive data via man-in-the-middle attacks due to missing SSL certificate validation in BlueStacks.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-pqpc-hhgr-p436

## What is CVE-2025-44964?

CVE-2025-44964 is a low-severity vulnerability in n/a, published on 5 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A lack of SSL certificate validation in BlueStacks v5.20 allows attackers to execute a man-it-the-middle attack and obtain sensitive information.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Bluestacks Bluestacks.

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

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

## Is CVE-2025-44964 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-0701](https://insights.sbomify.com/CVE-2018-0701/): Auth bypass in BlueStacks App Player (high 8.8)
- [CVE-2016-4288](https://insights.sbomify.com/CVE-2016-4288/): Privilege escalation in App Player (high 8.4)
- [CVE-2020-24367](https://insights.sbomify.com/CVE-2020-24367/): Privilege escalation in n/a (high 7.8)
- [CVE-2019-25548](https://insights.sbomify.com/CVE-2019-25548/): BlueStacks 4.80.0.1060 Denial of Service via Search Field (medium 6.9)
- [CVE-2019-14220](https://insights.sbomify.com/CVE-2019-14220/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44964 is a low-severity vulnerability in n/a, published on 5 Aug 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-44964 in the wild and no public exploit code.

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-44964/ (Markdown: https://insights.sbomify.com/CVE-2025-44964/index.md)
```

## Sources

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

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