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

> An attacker with physical access can extract unencrypted firmware to retrieve Wi-Fi credentials, enabling unauthorized network 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-qw84-c6vv-9c44

## What is CVE-2025-65825?

CVE-2025-65825 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 firmware on the basestation of the Meatmeet is not encrypted. An adversary with physical access to the Meatmeet device can disassemble the device, connect over UART, and retrieve the firmware dump for analysis. Within the NVS partition they may discover the credentials of the current and previous Wi-Fi networks. This information could be used to gain unauthorized access to the victim's Wi-Fi network.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Meatmeet Meatmeet Pro Wifi \& Bluetooth Meat Thermometer Firmware.

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

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

## Is CVE-2025-65825 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-65823](https://insights.sbomify.com/CVE-2025-65823/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-65824](https://insights.sbomify.com/CVE-2025-65824/): Missing authorization in n/a (high 8.8)
- [CVE-2025-65821](https://insights.sbomify.com/CVE-2025-65821/): Security feature bypass in n/a (high 7.5)
- [CVE-2025-65822](https://insights.sbomify.com/CVE-2025-65822/): Security feature bypass in n/a (medium 6.8)
- [CVE-2025-65829](https://insights.sbomify.com/CVE-2025-65829/): Security feature bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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