How severe is CVE-2025-65829?

CVE-2025-65829 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over physical access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-65829 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-65829?

CVE-2025-65829 affects Meatmeet Meatmeet Pro Wifi & Bluetooth Meat Thermometer Firmware. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-65829?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-65829 have an EU (EUVD) identifier?

Yes. CVE-2025-65829 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-202615.

When was CVE-2025-65829 published?

CVE-2025-65829 was published on 2025-12-10 and last updated on 2026-06-17.

CVE-2025-65829

CVE-2025-65829 is a medium-severity vulnerability in Meatmeet Meatmeet Pro Wifi & Bluetooth Meat Thermometer Firmware with a CVSS 3.x base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-94.

Key facts

Severity: Medium (CVSS 3.x base score 6.8)
EPSS exploit prediction: 0% (19th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-202615
Weakness: CWE-94
Affected product: Meatmeet Meatmeet Pro Wifi & Bluetooth Meat Thermometer Firmware
Published: 2025-12-10
Last modified: 2026-06-17

Description

The ESP32 system on a chip (SoC) that powers the Meatmeet basestation device was found to lack Secure Boot. The Secure Boot feature ensures that only authenticated software can execute on the device. The Secure Boot process forms a chain of trust by verifying all mutable software entities involved in the Application Startup Flow. As a result, an attacker with physical access to the device can flash modified firmware to the device, resulting in the execution of malicious code upon startup.

Frequently asked questions

What is CVE-2025-65829?: The ESP32 system on a chip (SoC) that powers the Meatmeet basestation device was found to lack Secure Boot. The Secure Boot feature ensures that only authenticated software can execute on the device. The Secure Boot process forms a chain of trust by verifying all mutable software entities involved in the Application Startup Flow. As a result, an attacker with physical access to the device can flash modified firmware to the device, resulting in the execution of malicious code upon startup.
How severe is CVE-2025-65829?: CVE-2025-65829 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over physical access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-65829 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-65829?: CVE-2025-65829 affects Meatmeet Meatmeet Pro Wifi & Bluetooth Meat Thermometer Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-65829?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-65829 have an EU (EUVD) identifier?: Yes. CVE-2025-65829 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-202615.
When was CVE-2025-65829 published?: CVE-2025-65829 was published on 2025-12-10 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:o:meatmeet:meatmeet_pro_wifi_\&_bluetooth_meat_thermometer_firmware:1.0.34.4:*:*:*:*:*:*:*

More vulnerabilities in Meatmeet Meatmeet Pro Wifi & Bluetooth Meat Thermometer Firmware

CVE-2025-65823 — Critical (CVSS 9.8): The Meatmeet Pro was found to be shipped with hardcoded Wi-Fi credentials in the firmware, for the test network it was…
CVE-2025-65824 — High (CVSS 8.8): An unauthenticated attacker within proximity of the Meatmeet device can perform an unauthorized Over The Air (OTA)…
CVE-2025-65821 — High (CVSS 7.5): As UART download mode is still enabled on the ESP32 chip on which the firmware runs, an adversary can dump the flash…
CVE-2025-65822 — Medium (CVSS 6.8): The ESP32 system on a chip (SoC) that powers the Meatmeet Pro was found to have JTAG enabled. By leaving JTAG enabled…
CVE-2025-65828 — Medium (CVSS 6.5): An unauthenticated attacker within proximity of the Meatmeet device can issue several commands over Bluetooth Low…
CVE-2025-65825 — Medium (CVSS 4.6): The firmware on the basestation of the Meatmeet is not encrypted. An adversary with physical access to the Meatmeet…

All CVEs affecting Meatmeet Meatmeet Pro Wifi & Bluetooth Meat Thermometer Firmware →

Other CWE-94 (Code Injection) vulnerabilities

CVE-2026-57624 — Critical (CVSS 10.0): Unauthenticated Remote Code Execution (RCE) in Blocksy Companion Pro <= 2.1.46 versions.
CVE-2026-10134 — Critical (CVSS 10.0): IBM Langflow OSS 1.0.0 through 1.9.3 allows an attacker to read every secret available to the Langflow process, read…
CVE-2026-53576 — Critical (CVSS 10.0): Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter…
CVE-2026-10561 — Critical (CVSS 10.0): IBM Langflow OSS 1.0.0 through 1.9.3 has an vulnerability due to an improper isolation of Python execution combined…
CVE-2026-25470 — Critical (CVSS 10.0): Improper Control of Generation of Code ('Code Injection') vulnerability in ACPT ACPT (Pro) - Custom Post Types Plugin…
CVE-2026-48836 — Critical (CVSS 10.0): Unauthenticated Remote Code Execution (RCE) in Easy Invoice <= 2.1.19 versions.

Browse all CWE-94 (Code Injection) vulnerabilities →