# CVE-2025-52464: Meshtastic Repeated Public and Private Keypairs

> Attackers can decrypt private messages if devices use duplicated or low-entropy keys due to flawed initialization or vendor flashing.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:L/SI:L/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** CVE-2025-54797, GHSA-gq7v-jr8c-mfr7

## What is CVE-2025-52464?

CVE-2025-52464 is a critical vulnerability in meshtastic firmware, published on 19 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Meshtastic is an open source mesh networking solution. In versions from 2.5.0 to before 2.6.11, the flashing procedure of several hardware vendors was resulting in duplicated public/private keys. Additionally, the Meshtastic was failing to properly initialize the internal randomness pool on some platforms, leading to possible low-entropy key generation. When users with an affected key pair sent Direct Messages, those message could be captured and decrypted by an attacker that has compiled the list of compromised keys. This issue has been patched in version 2.6.11 where key generation is delayed til the first time the LoRa region is set, along with warning users when a compromised key is detected. Version 2.6.12 furthers this patch by automatically wiping known compromised keys when found. A workaround to this vulnerability involves users doing a complete device wipe to remove vendor-cloned keys.

Weakness: CWE-331 (Insufficient Entropy)

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

It affects 1 product.


Products: Meshtastic Meshtastic Firmware.

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

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

## Is CVE-2025-52464 being exploited?

There is no known exploitation of CVE-2025-52464 in the wild and no public exploit code.

Public exploit code:

- Software-only proof of concept for CVE-2025-52464 in Meshtastic Direct Messages (github_poc): https://github.com/msdmehdipour/meshtastic-cve-2025-52464-poc

## Other vulnerabilities in meshtastic firmware

- [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)
- [CVE-2026-42566](https://insights.sbomify.com/CVE-2026-42566/): Meshtastic: Malformed UTF-8 in User.long_name broadcast over LoRa causes mesh-wide client decode failure (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52464 is a critical vulnerability in meshtastic firmware, published on 19 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52464 in the wild and no public exploit code.

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-52464/ (Markdown: https://insights.sbomify.com/CVE-2025-52464/index.md)
```

## Sources

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

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