Severe Meshtastic Flaw Exposes Encrypted Messages to Attackers

A severe cryptographic flaw (CVE-2025-52464, CVSSv4 9.5) has been discovered in the Meshtastic firmware, exposing users to message decryption and remote node hijacking.

The vulnerability stems from duplicated X25519 public/private key pairs and insufficient entropy during key generation, affecting devices running firmware versions >2.5.0.

Patched in version 2.6.11, this issue impacts Meshtastic’s Direct Message (DM) encryption and remote administration features.

Root Causes:

The vulnerability originates from two critical failures in the cryptographic implementation:

1. Vendor Cloning Practices: Hardware manufacturers created “golden images” by flashing one device, letting it generate keys at first boot, then cloning that image to multiple units.
2. This resulted in identical X25519 keypairs across entire production batches.
3. Low-Entropy Key Generation: The rweather/crypto library failed to initialize randomness pools on platforms like NRF52 properly. Instead of using hardware entropy sources, it relied on micros() timestamps, creating predictable keys.
4. On Arduino platforms, the library didn’t call random() at all, exacerbating the entropy deficit.

Exploitation Scenarios and Impacts

Attackers exploiting this vulnerability gain two primary attack vectors:

• Direct Message Decryption: Compromised keys allow decryption of private DMs sent between devices.
• An attacker with a compiled list of duplicated keys can passively intercept and decrypt messages.
• Remote Node Hijacking: If a compromised key is added as a remote administrator, attackers can issue commands to nodes.
• For nodes with compromised keys, attackers can derive shared_key using an administrator’s public key to impersonate legitimate admins.
• This enables full command execution on affected nodes.

Mitigations and Security Upgrades

Meshtastic’s firmware update (v2.6.11) implements three key fixes:

1. Key Generation Delay: Keys now generate only after the user sets the LoRa region, preventing vendor cloning during mass production.
2. Entropy Enhancements: Added random() outputs and hardware IDs to seed the crypto library’s randomness pool, improving key uniqueness.
3. Compromised Key Detection: Devices now warn users when duplicated keys are detected. Future version 2.6.12 will automatically wipe known compromised keys.

For immediate remediation, users can:

• Execute a factory reset via CLI: meshtastic --factory-reset-device
• Generate high-entropy keys using OpenSSL:

bashopenssl genpkey -algorithm x25519 -outform DER | tail -c32 | base64

This vulnerability underscores the challenges of secure key generation in resource-constrained IoT environments.

Users should upgrade to v2.6.11 immediately and regenerate keys using the OpenSSL method for maximum security.

Find this Story Interesting! Follow us on LinkedIn and X to Get More Instant updates

The post Severe Meshtastic Flaw Exposes Encrypted Messages to Attackers appeared first on Cyber Security News.