Meshtastic up to 2.6.2 Direct Message less trusted source

Summaryinfo

A vulnerability identified as critical has been detected in Meshtastic up to 2.6.2. This issue affects some unknown processing of the component Direct Message Handler. Performing a manipulation results in less trusted source. This vulnerability is cataloged as CVE-2025-55292. It is possible to initiate the attack remotely. There is no exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Meshtastic up to 2.6.2. It has been classified as critical. This affects some unknown functionality of the component Direct Message Handler. The manipulation with an unknown input leads to a less trusted source vulnerability. CWE is classifying the issue as CWE-348. The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Meshtastic is an open source mesh networking solution. In the current Meshtastic architecture, a Node is identified by their NodeID, generated from the MAC address, rather than their public key. This aspect downgrades the security, specifically by abusing the HAM mode which doesn't use encryption. An attacker can, as such, forge a NodeInfo on behalf of a victim node advertising that the HAM mode is enabled. This, in turn, will allow the other nodes on the mesh to accept the new information and overwriting the NodeDB. The other nodes will then only be able to send direct messages to the victim by using the shared channel key instead of the PKC. Additionally, because HAM mode by design doesn't provide any confidentiality or authentication of information, the attacker could potentially also be able to change the Node details, like the full name, short code, etc. To keep the attack persistent, it is enough to regularly resend the forged NodeInfo, in particular right after the victim sends their own. A patch is available in version 2.7.6.834c3c5.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-55292 since 08/12/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Applying the patch e5e8683cdba133e726033101586c3235a8678893 is able to eliminate this problem. The bugfix is ready for download at github.com.

The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202601-4628). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Meshtastic

Version

• 2.6.0
• 2.6.1
• 2.6.2

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion