CVE-2025-24798Public exploit

Node crash via reachable routing reply assertion

Published Jul 10, 2025 · Updated Jul 11, 2025

Reachable assertion in Meshtastic Firmware 1.2.1 through 2.6.1 allows remote attackers to crash nodes with a crafted routing packet. RoutingModule::allocReply treats a ROUTING_APP request with want_response set as an impossible state and executes assert(0), aborting the firmware process. No authentication or user interaction is required; radio-range senders can crash nearby nodes, while MQTT delivery also reaches nodes sharing a topic when downlink is enabled.

CVSS severity4.3
Medium
EPSS probability0.39%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Reachable assertion in Meshtastic Firmware 1.2.1 through 2.6.1 allows remote attackers to crash nodes with a crafted routing packet. RoutingModule::allocReply treats a ROUTING_APP request with want_response set as an impossible state and executes assert(0), aborting the firmware process. No authentication or user interaction is required; radio-range senders can crash nearby nodes, while MQTT delivery also reaches nodes sharing a topic when downlink is enabled.

The record

CVE
CVE-2025-24798
Published
Jul 10, 2025
Updated
Jul 11, 2025
Vendor
Meshtastic
Product
Meshtastic Firmware
Classifications
CWE-617, T1499.004
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 10, 2025CVE publishedPublication date reported by the CVE source.
  2. Jul 11, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.2.1, < 2.6.2

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Meshtastic · Meshtastic Firmwareversion=>= 1.2.1, < 2.6.2

Published CVSS scores

6.5NIST NVDCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.3GitHub, Inc.CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-617Reachable Assertion
T1499.004Endpoint Denial of Service: Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo