Vulnerability Description
Meshtastic is an open source mesh networking solution. The Meshtastic firmware (starting from version 2.5) introduces asymmetric encryption (PKI) for direct messages, but when the `pki_encrypted` flag is missing, the firmware silently falls back to legacy AES-256-CTR channel encryption. This was an intentional decision to maintain backwards compatibility. However, the end-user applications, like Web app, iOS/Android app, and applications built on top of Meshtastic using the SDK, did not have a way to differentiate between end-to-end encrypted DMs and the legacy DMs. This creates a downgrade attack path where adversaries who know a shared channel key can craft and inject spoofed direct messages that are displayed as if they were PKC encrypted. Users are not given any feedback of whether a direct message was decrypted with PKI or with legacy symmetric encryption, undermining the expected security guarantees of the PKI rollout. Version 2.7.15 fixes this issue.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Meshtastic | Meshtastic Firmware | >= 2.5.0, < 2.7.15 |
Related Weaknesses (CWE)
References
- https://github.com/meshtastic/firmware/security/advisories/GHSA-377p-prwp-4hwfExploitVendor Advisory
FAQ
What is CVE-2025-53627?
CVE-2025-53627 is a vulnerability with a CVSS score of 5.3 (MEDIUM). Meshtastic is an open source mesh networking solution. The Meshtastic firmware (starting from version 2.5) introduces asymmetric encryption (PKI) for direct messages, but when the `pki_encrypted` flag...
How severe is CVE-2025-53627?
CVE-2025-53627 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-53627?
Check the references section above for vendor advisories and patch information. Affected products include: Meshtastic Meshtastic Firmware.