CVE-2024-47078 Meshtastic firmware Authentication/Authorization Bypass via MQTT
Attackers can bypass MQTT authentication to gain unauthorized control over Meshtastic mesh network nodes.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-47078?
CVE-2024-47078 is a high-severity authentication bypass vulnerability in meshtastic firmware, published on 25 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Meshtastic is an open source, off-grid, decentralized, mesh network. Meshtastic uses MQTT to communicate over an internet connection to a shared or private MQTT Server. Nodes can communicate directly via an internet connection or proxied through a connected phone (i.e., via bluetooth). Prior to version 2.5.1, multiple weaknesses in the MQTT implementation allow for authentication and authorization bypasses resulting in unauthorized control of MQTT-connected nodes. Version 2.5.1 contains a patch.
Which versions are affected by CVE-2024-47078?
It affects 1 product.
Products include Meshtastic Meshtastic Firmware.
How do I fix CVE-2024-47078?
No fix has been published for CVE-2024-47078 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2024-47078 being exploited?
There is no known exploitation of CVE-2024-47078 in the wild and no public exploit code.
Other vulnerabilities in meshtastic firmware
- CVE-2025-52464 Meshtastic Repeated Public and Private Keypairs
- CVE-2025-55293 Meshtastic allows crafting of specific NodeInfo packets that overwrite any publicKey saved in the NodeDB
- CVE-2025-24797 Meshtastic incorrectly hands malformed packets leads to controlled buffer overflow
- CVE-2025-55292 In Meshtastic, an attacker can spoof licensed amateur flag for a node
- CVE-2026-42566 Meshtastic: Malformed UTF-8 in User.long_name broadcast over LoRa causes mesh-wide client decode failure