# CVE-2025-65832: Information disclosure in n/a

> An attacker with physical access can dump memory to retrieve Wi-Fi credentials and JWTs, enabling unauthorized network and account access.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-fj4x-vq3p-rjcf

## What is CVE-2025-65832?

CVE-2025-65832 is a medium-severity vulnerability in n/a, published on 10 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The mobile application insecurely handles information stored within memory. By performing a memory dump on the application after a user has logged out and terminated it, Wi-Fi credentials sent during the pairing process, JWTs used for authentication, and other sensitive details can be retrieved. As a result, an attacker with physical access to the device of a victim can retrieve this information and gain unauthorized access to their home Wi-Fi network and Meatmeet account.

Weakness: CWE-316 (Cleartext Storage of Sensitive Information in Memory)

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

It affects 1 product.


Products: Meatmeet Meatmeet.

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

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

## Is CVE-2025-65832 being exploited?

There is no known exploitation of CVE-2025-65832 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-65827](https://insights.sbomify.com/CVE-2025-65827/): Weak cryptography in n/a (critical 9.1)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65832 is a medium-severity vulnerability in n/a, published on 10 Dec 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-65832 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-65832/ (Markdown: https://insights.sbomify.com/CVE-2025-65832/index.md)
```

## Sources

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

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