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

> Attackers can intercept HTTP traffic and crack MD5 hashes to take over user accounts due to insecure mobile app configuration.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-hpx6-2j8w-26mq

## What is CVE-2025-65827?

CVE-2025-65827 is a critical vulnerability in n/a, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The mobile application is configured to allow clear text traffic to all domains and communicates with an API server over HTTP. As a result, an adversary located "upstream" can intercept the traffic, inspect its contents, and modify the requests in transit. TThis may result in a total compromise of the user's account if the attacker intercepts a request with active authentication tokens or cracks the MD5 hash sent on login.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Meatmeet Meatmeet.

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

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

## Is CVE-2025-65827 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-65820](https://insights.sbomify.com/CVE-2025-65820/): Information disclosure in n/a (critical 9.8)
- [CVE-2025-65826](https://insights.sbomify.com/CVE-2025-65826/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-65830](https://insights.sbomify.com/CVE-2025-65830/): Weak cryptography in n/a (critical 9.1)
- [CVE-2025-65831](https://insights.sbomify.com/CVE-2025-65831/): Weak cryptography in n/a (high 7.5)
- [CVE-2025-65832](https://insights.sbomify.com/CVE-2025-65832/): Information disclosure in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65827 is a critical vulnerability in n/a, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-65827 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-65827/ (Markdown: https://insights.sbomify.com/CVE-2025-65827/index.md)
```

## Sources

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

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