# CVE-2025-24798: Meshtastic crashes via an unimplemented routing module reply

> A malicious packet causes Meshtastic nodes to crash, degrading service for nearby devices or via MQTT downlink.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2025
- **Updated:** 11 Jul 2025
- **Also known as:** GHSA-4q84-546j-3mf5

## What is CVE-2025-24798?

CVE-2025-24798 is a medium-severity denial of service vulnerability in meshtastic firmware, published on 10 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2025-24798?

It affects 1 product.


Products: Meshtastic Meshtastic Firmware.

## How do I fix CVE-2025-24798?

No fix has been published for CVE-2025-24798 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24798 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24798 exists.

## Other vulnerabilities in meshtastic firmware

- [CVE-2025-52464](https://insights.sbomify.com/CVE-2025-52464/): Meshtastic Repeated Public and Private Keypairs (critical 9.5)
- [CVE-2025-55293](https://insights.sbomify.com/CVE-2025-55293/): Meshtastic allows crafting of specific NodeInfo packets that overwrite any publicKey saved in the NodeDB (critical 9.4)
- [CVE-2025-24797](https://insights.sbomify.com/CVE-2025-24797/): Meshtastic incorrectly hands malformed packets leads to controlled buffer overflow (critical 9.4)
- [CVE-2025-55292](https://insights.sbomify.com/CVE-2025-55292/): In Meshtastic, an attacker can spoof licensed amateur flag for a node (high 8.2)
- [CVE-2024-47078](https://insights.sbomify.com/CVE-2024-47078/): Meshtastic firmware Authentication/Authorization Bypass via MQTT (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24798 and fix it if it is affected.

What it is: CVE-2025-24798 is a medium-severity denial of service vulnerability in meshtastic firmware, published on 10 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24798 exists.

Affected product: meshtastic firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24798/ (Markdown: https://insights.sbomify.com/CVE-2025-24798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24798
- OSV: https://osv.dev/vulnerability/CVE-2025-24798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24798/
Summaries are generated and may contain mistakes; the official description above is the record.