CVE-2025-53627CWE-1287

CVE-2025-53627

Medium · published December 29, 2025

CVSS v3.1
5.3
EPSS
0%
Percentile
9.3
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
5.3 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CVSS v4.0
Not supplied
EPSS
0.00200 · 9.3th percentile
Weakness
CWE-1287 · Improper Validation of Specified Type of Input
Published
2025-12-29T22:15Z
Affected products (1)
ProductVersionsFixed in
meshtastic/meshtastic_firmware≥ 2.5.0, < 2.7.152.7.15
References (1)
EPSS history
Timeline
  • 29 DEC 16:18Z
    Meshtastic firmware allows forged DMs with no PKC to show up as encrypted
    cvelistv5