Read the docs
TI-2025-34948 Aliases CVE-2025-55292

In Meshtastic, an attacker can spoof licensed amateur flag for a node

Priority HIGH 75CWE-348Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
High · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00144 3rd percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
meshtasticfirmwareup to 2.6.2—No fix listedCNA
  • firmware Vendormeshtastic Affected up to 2.6.2 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:o:meshtastic:meshtastic_firmware:*:*:*:*:*:*:*:*before 2.7.6Vulnerablemeshtastic
  • cpe:2.3:o:meshtastic:meshtastic_firmware:*:*:*:*:*:*:*:* Versions before 2.7.6 Vulnerable ·meshtastic

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2025-55292

References

  • TI-2025-34949 Meshtastic allows crafting of specific NodeInfo packets that overwrite any publicKey saved in the NodeDB CVSS 3.1CRITICAL 9.8
  • TI-2024-34421 Failure to check for packets from the broadcast address allows potential DDoS… CVSS 3.1HIGH 7.5
  • TI-2025-33563 Meshtastic allows Command Injection in GitHub Action CVSS 3.1HIGH 8.0
  • TI-2025-18515 Meshtastic crashes via an unimplemented routing module reply CVSS 3.1MEDIUM 6.5
  • TI-2025-33554 Meshtastic firmware allows forged DMs with no PKC to show up as encrypted CVSS 3.1MEDIUM 5.3
  • TI-2024-31447 Traceroute_APP responses are not rate-limited. CVSS 4.0LOW 2.7
See all 13 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences