CVE-2025-53627
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 Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Threat Intelligence
Weaknesses 1
Affected Products 1
| Vendor | Product | Version | Range |
|---|---|---|---|
| meshtastic | meshtastic_firmware | * | ≥2.5.0 – <2.7.15 |
References 1
- github.com https://github.com/meshtastic/firmware/security/advisories/GHSA-377p-prwp-4hwf
Remediation
No remediation data recorded yet
Check vendor advisories and the NVD entry for patch availability.