CVE-2025-55293: CWE-287: Improper Authentication in meshtastic firmware
Meshtastic is an open source mesh networking solution. Prior to v2.6.3, an attacker can send NodeInfo with a empty publicKey first, then overwrite it with a new key. First sending a empty key bypasses 'if (p.public_key.size > 0) {', clearing the existing publicKey (and resetting the size to 0) for a known node. Then a new key bypasses 'if (info->user.public_key.size > 0) {', and this malicious key is stored in NodeDB. This vulnerability is fixed in 2.6.3.
AI Analysis
Technical Summary
CVE-2025-55293 is a critical improper authentication vulnerability (CWE-287) found in the Meshtastic firmware versions prior to 2.6.3. Meshtastic is an open-source mesh networking solution that enables decentralized communication between devices. The vulnerability arises from flawed handling of the NodeInfo public key updates. Specifically, an attacker can first send a NodeInfo message with an empty publicKey, which bypasses the check 'if (p.public_key.size > 0)' and clears the existing publicKey for a known node by resetting its size to zero. Subsequently, the attacker sends a new NodeInfo message with a malicious publicKey. This second message bypasses the check 'if (info->user.public_key.size > 0)' because the size was reset, allowing the malicious key to be stored in the NodeDB. This sequence effectively allows an attacker to overwrite the legitimate public key of a node with a malicious one without authentication or user interaction. The vulnerability has a CVSS 3.1 base score of 9.4 (critical), reflecting its high impact and ease of exploitation over the network without privileges or user interaction. The impact includes full compromise of confidentiality and integrity of mesh communications, as the attacker can impersonate nodes, intercept, modify, or inject messages, and potentially disrupt network availability. The vulnerability was fixed in Meshtastic firmware version 2.6.3.
Potential Impact
For European organizations using Meshtastic mesh networking devices, this vulnerability poses a significant risk. The ability to overwrite node public keys without authentication allows attackers to impersonate legitimate nodes, intercept sensitive communications, and manipulate data integrity within the mesh network. This could lead to unauthorized data disclosure, disruption of critical communications, and potential sabotage of network operations. Organizations relying on Meshtastic for secure communications in sectors such as emergency services, outdoor activities, or industrial IoT could face operational disruptions and data breaches. Given the critical severity and network-level exploitability, the threat is especially concerning for organizations operating in environments where mesh networking is integral to communication infrastructure.
Mitigation Recommendations
European organizations should immediately upgrade all Meshtastic devices to firmware version 2.6.3 or later, where this vulnerability is patched. In addition to patching, organizations should implement strict network segmentation to isolate mesh networks from broader enterprise networks, limiting exposure. Monitoring network traffic for anomalous NodeInfo messages, especially those with empty or suspicious public keys, can help detect exploitation attempts. Employing cryptographic validation and integrity checks on NodeInfo updates beyond the firmware's built-in checks can add an additional layer of defense. Organizations should also maintain an inventory of all Meshtastic devices and enforce strict access controls to prevent unauthorized device configuration or message injection. Finally, educating users and administrators about this vulnerability and the importance of timely updates is critical to reduce risk.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Norway, Finland, Poland, Italy, Spain
CVE-2025-55293: CWE-287: Improper Authentication in meshtastic firmware
Description
Meshtastic is an open source mesh networking solution. Prior to v2.6.3, an attacker can send NodeInfo with a empty publicKey first, then overwrite it with a new key. First sending a empty key bypasses 'if (p.public_key.size > 0) {', clearing the existing publicKey (and resetting the size to 0) for a known node. Then a new key bypasses 'if (info->user.public_key.size > 0) {', and this malicious key is stored in NodeDB. This vulnerability is fixed in 2.6.3.
AI-Powered Analysis
Technical Analysis
CVE-2025-55293 is a critical improper authentication vulnerability (CWE-287) found in the Meshtastic firmware versions prior to 2.6.3. Meshtastic is an open-source mesh networking solution that enables decentralized communication between devices. The vulnerability arises from flawed handling of the NodeInfo public key updates. Specifically, an attacker can first send a NodeInfo message with an empty publicKey, which bypasses the check 'if (p.public_key.size > 0)' and clears the existing publicKey for a known node by resetting its size to zero. Subsequently, the attacker sends a new NodeInfo message with a malicious publicKey. This second message bypasses the check 'if (info->user.public_key.size > 0)' because the size was reset, allowing the malicious key to be stored in the NodeDB. This sequence effectively allows an attacker to overwrite the legitimate public key of a node with a malicious one without authentication or user interaction. The vulnerability has a CVSS 3.1 base score of 9.4 (critical), reflecting its high impact and ease of exploitation over the network without privileges or user interaction. The impact includes full compromise of confidentiality and integrity of mesh communications, as the attacker can impersonate nodes, intercept, modify, or inject messages, and potentially disrupt network availability. The vulnerability was fixed in Meshtastic firmware version 2.6.3.
Potential Impact
For European organizations using Meshtastic mesh networking devices, this vulnerability poses a significant risk. The ability to overwrite node public keys without authentication allows attackers to impersonate legitimate nodes, intercept sensitive communications, and manipulate data integrity within the mesh network. This could lead to unauthorized data disclosure, disruption of critical communications, and potential sabotage of network operations. Organizations relying on Meshtastic for secure communications in sectors such as emergency services, outdoor activities, or industrial IoT could face operational disruptions and data breaches. Given the critical severity and network-level exploitability, the threat is especially concerning for organizations operating in environments where mesh networking is integral to communication infrastructure.
Mitigation Recommendations
European organizations should immediately upgrade all Meshtastic devices to firmware version 2.6.3 or later, where this vulnerability is patched. In addition to patching, organizations should implement strict network segmentation to isolate mesh networks from broader enterprise networks, limiting exposure. Monitoring network traffic for anomalous NodeInfo messages, especially those with empty or suspicious public keys, can help detect exploitation attempts. Employing cryptographic validation and integrity checks on NodeInfo updates beyond the firmware's built-in checks can add an additional layer of defense. Organizations should also maintain an inventory of all Meshtastic devices and enforce strict access controls to prevent unauthorized device configuration or message injection. Finally, educating users and administrators about this vulnerability and the importance of timely updates is critical to reduce risk.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-08-12T16:15:30.237Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68a3673ead5a09ad00b0dda5
Added to database: 8/18/2025, 5:47:42 PM
Last enriched: 8/18/2025, 6:02:48 PM
Last updated: 11/17/2025, 11:57:22 PM
Views: 133
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-13306: Command Injection in D-Link DWR-M920
MediumCVE-2025-13230: Type Confusion in Google Chrome
HighCVE-2025-13229: Type Confusion in Google Chrome
HighCVE-2025-13228: Type Confusion in Google Chrome
HighCVE-2025-13227: Type Confusion in Google Chrome
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.