dbcve.org
Meatmeet Pro Wifi \& Bluetooth Meat Thermometer FirmwareOperating system · Meatmeet

CVE-2025-65821

HIGH · 7.5 CVSS v3.1 Published 2025-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
As UART download mode is still enabled on the ESP32 chip on which the firmware runs, an adversary can dump the flash from the device and retrieve sensitive information such as details about the current and previous Wi-Fi network from the NVS partition. Additionally, this allows the adversary to reflash the device with their own firmware which may contain malicious modifications.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

UART download mode remains enabled on the ESP32 chip, allowing an attacker with physical access to dump the flash memory via the UART interface. This exposes sensitive data stored in the NVS partition, including current and previous Wi-Fi network credentials. Additionally, the enabled debug interface permits the adversary to reflash the device with malicious firmware.

MitigationDisable UART download mode by configuring the appropriate eFuse bits (e.g., DIS_DOWNLOAD_MODE, DIS_JTAG) and enable flash encryption and secure boot to prevent unauthorized flash access and firmware modification.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Meatmeet Pro Wifi \& Bluetooth Meat Thermometer FirmwareOperating system
Affected:= 1.0.34.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the firmware version
    Connect to the device via UART (commonly at 115200 baud) and query the firmware version using esptool.py with command: python esptool.py -p /dev/ttyUSB0 chip_id, or check boot logs for version string
    Affected if The firmware version is exactly 1.0.34.4 on the Meatmeet Meatmeet Pro Wifi & Bluetooth Meat Thermometer
  2. Verify UART download mode is accessible
    Attempt to connect to the device UART interface and check if esptool can communicate with the chip. Run: python esptool.py -p /dev/ttyUSB0 read_flash_status, which will succeed if download mode is enabled
    Affected if esptool successfully communicates with the ESP32 chip via UART, indicating download mode is not locked down
  3. Check eFuse DIS_DOWNLOAD_MODE bit
    Run: python esptool.py -p /dev/ttyUSB0 dump_crypto_config or read eFuse summary to inspect the DIS_DOWNLOAD_MODE eFuse bit
    Affected if The DIS_DOWNLOAD_MODE eFuse bit is unset (value 0), meaning UART download mode remains enabled
  4. Check eFuse DIS_JTAG bit
    Run: python esptool.py -p /dev/ttyUSB0 read_crypto_config to inspect the DIS_JTAG bit in eFuse
    Affected if The DIS_JTAG eFuse bit is unset (value 0), indicating JTAG debug interface remains accessible
  5. Verify flash encryption status
    Run: python esptool.py -p /dev/ttyUSB0 get_secure_version to check if flash encryption is enabled, or inspect boot logs for encryption indicators
    Affected if Flash encryption is not enabled (unencrypted flash contents readable)
  6. Test ability to dump flash contents
    Attempt to read flash memory via UART: python esptool.py -p /dev/ttyUSB0 read_flash 0x0 0x400000 flash_dump.bin
    Affected if The command succeeds and produces a readable flash dump, confirming the device is vulnerable

If the device runs firmware 1.0.34.4 on the Meatmeet Meatmeet Pro and UART download mode is accessible (DIS_DOWNLOAD_MODE eFuse unset), the device is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable UART download mode by configuring the appropriate eFuse bits (e.g., DIS_DOWNLOAD_MODE, DIS_JTAG) and enable flash encryption and secure boot to prevent unauthorized flash access and firmware modification.

Fix this in Meatmeet Pro Wifi \& Bluetooth Meat Thermometer Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65821 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65821 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data