CVE-2025-55292 Details
Description
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.
A vulnerability exists in Meshtastic, an open-source mesh networking solution, where nodes are identified by their NodeID derived from the MAC address instead of their public key. This flaw weakens security by exploiting the HAM mode, which lacks encryption. An attacker can forge NodeInfo for a victim node, falsely claiming that HAM mode is active. This deception enables the attacker to manipulate the victim's NodeDB, allowing direct messages to be sent using the shared channel key instead of the public key cryptography (PKC) key. Furthermore, the attacker could alter the victim node's details, such as the full name or short code. To maintain this attack, the forged NodeInfo must be regularly resent, particularly after the victim node transmits its own.
Users are advised to utilize the NodeDB feature as an append-only file to prevent overwriting existing node information. Additionally, when a device switches to HAM mode, it should generate a new NodeID based on a different MAC address to avoid conflicts with the PKC mode identification.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 28, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/meshtastic/firmware/commit/e5e8683cdba133e726033101586c3235a8678893 | [email protected] | Patch |
| https://github.com/meshtastic/firmware/security/advisories/GHSA-45vg-3f35-7ch2 | [email protected] | ExploitMitigationVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-348 | Use of Less Trusted Source | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| meshtastic meshtastic firmware | < 2.7.6 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Mar 2, 2026 | Initial Analysis | [email protected] |
| Jan 28, 2026 | New CVE Received | [email protected] |