CRITICAL🇵🇱 Wersja polska

CVE-2025-52464

CVSS 9.5v4.0pub. 2025-06-19upd. 2025-10-09

Meshtastic is an open source mesh networking solution. In versions from 2.5.0 to before 2.6.11, the flashing procedure of several hardware vendors was resulting in duplicated public/private keys. Additionally, the Meshtastic was failing to properly initialize the internal randomness pool on some platforms, leading to possible low-entropy key generation. When users with an affected key pair sent Direct Messages, those message could be captured and decrypted by an attacker that has compiled the list of compromised keys. This issue has been patched in version 2.6.11 where key generation is delayed til the first time the LoRa region is set, along with warning users when a compromised key is detected. Version 2.6.12 furthers this patch by automatically wiping known compromised keys when found. A workaround to this vulnerability involves users doing a complete device wipe to remove vendor-cloned keys.

🤖 AI Analysis
How it works

The problem results from two related flaws: first, flashing processors used by hardware manufacturers duplicated identical key pairs across multiple devices; second, the firmware software did not properly initialize the internal entropy pool (randomness) on some platforms, leading to the generation of low-entropy keys (CWE-331 — insufficient entropy). An attacker who compiles a list of known compromised keys can intercept encrypted direct messages sent by users possessing vulnerable key pairs and then decrypt them.

Impact

An attacker is able to decrypt private direct messages transmitted by devices with vulnerable keys, which means complete compromise of communication confidentiality. In case of key compromise at the system level, limited impact on integrity and availability of dependent systems is also possible.

Mitigation & patch

Update firmware to version 2.6.11, which delays key generation until the first LoRa region setting and warns the user of detected compromised keys. Version 2.6.12 extends the fix by automatically removing known compromised keys upon detection. As a workaround, a complete device wipe is recommended to remove keys cloned by the manufacturer.

Who is affected

Meshtastic Firmware versions from 2.5.0 to before 2.6.11, particularly devices whose keys were generated during the flashing procedure by hardware manufacturers using duplicated keys or platforms with improper randomness pool initialization.

Analysis generated by Claude AI (Anthropic) based on NVD data. Always verify with vendor.
CVSS Vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:L/SI:L/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
  • Meshtastic Firmware

    OS
    Meshtastic
    2.5.0 – 2.6.11 (excl.)
🔵
CHECK WITH VENDOR
No clear patch data available. Check vendor references.
CWE
References

Related vulnerabilities

CVE-2025-55293CRITICAL9.4PL ✓same product

Meshtastic Firmware: pominięcie uwierzytelnienia przez podmianę klucza publicznego

CVE-2025-24797CRITICAL9.4PL ✓same product

RCE przez buffer overflow w obsłudze pakietów protobuf w Meshtastic Firmware

CVE-2026-42566HIGH7.5PL ✓same product

Meshtastic: nieprawidłowe kodowanie nazwy węzła powoduje DoS przez BLE

CVE-2025-55292HIGH8.2same product

Meshtastic is an open source mesh networking solution. In the current Meshtastic architecture, a Node is ident...

CVE-2024-47078HIGH8.1same product

Meshtastic is an open source, off-grid, decentralized, mesh network. Meshtastic uses MQTT to communicate over ...