CVE-2025-24798VulnerabilityPublished 10 Jul 2025

CVE-2025-24798: meshtastic firmware · Reachable Assertion

Affects meshtastic firmwareSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.6.2 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.6.2

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade meshtastic/firmware to 2.6.2.

Affected software

Product	Affected	Fixed in
GitHubmeshtastic/firmware`pkg:github/meshtastic/firmware`Other threats	Affected >=1.2.1 <2.6.2	Fixed in 2.6.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should promptly upgrade all Meshtastic firmware instances to version 2.6.2 or later to eliminate the vulnerability. For deployments where immediate upgrade is not feasible, network administrators should implement filtering rules to block packets with the 'want_response' flag set to true at the network edge or routing module level, if possible. Disabling MQTT downlink functionality temporarily can reduce the attack surface for remote exploitation. Additionally, monitoring mesh network nodes for unexpected crashes or service degradation can help detect exploitation attempts early. Organizations should also segment mesh network management traffic from other network segments to limit exposure. Implementing anomaly detection on MQTT traffic and wireless packets can provide early warning of malicious activity. Finally, incorporating redundancy in mesh network design can mitigate the impact of individual node crashes by maintaining alternative communication paths.

Description

Meshtastic is an open source mesh networking solution. From 1.2.1 until 2.6.2, a packet sent to the routing module that contains want_response==true causes a crash. This can lead to a degradation of service for nodes within range of a malicious sender, or via MQTT if downlink is enabled. This vulnerability is fixed in 2.6.2.

Impact

For European organizations utilizing Meshtastic-based mesh networks, particularly in critical communication scenarios such as emergency services, outdoor event coordination, or remote monitoring, this vulnerability poses a risk of service disruption. The crash induced by malicious packets can degrade network reliability and availability, potentially interrupting communication in areas relying on these mesh nodes. Organizations using MQTT downlink to manage or update nodes remotely face an increased risk, as attackers could exploit the vulnerability remotely without physical proximity. This could impact sectors such as public safety, environmental monitoring, and industrial IoT deployments where mesh networks are deployed for resilient communication. Although the vulnerability does not compromise data confidentiality or integrity, the denial of service effect could hinder operational continuity and emergency responsiveness. The medium severity rating indicates a moderate risk level, but the impact could be significant in environments where mesh network availability is critical.

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
Implementation · Input Validation
Perform input validation on user data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2025, 21:46 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats