Cyber Resilience

CVE-2025-53627

Meshtastic Firmware 2.5.0 – 2.7.15

Public PoC
Published
29 December 2025
Modified
26 February 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0019 9th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2025-53627 is a medium-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Meshtastic Meshtastic Firmware. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-1287

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-24797Same product: Meshtastic Meshtastic Firmware
CVE-2024-51500Same product: Meshtastic Meshtastic Firmware
CVE-2024-47078Same product: Meshtastic Meshtastic Firmware
CVE-2024-45038Same product: Meshtastic Meshtastic Firmware
CVE-2025-53637Same product: Meshtastic Meshtastic Firmware
CVE-2025-55293Same product: Meshtastic Meshtastic Firmware
CVE-2025-24798Same product: Meshtastic Meshtastic Firmware
CVE-2025-52464Same product: Meshtastic Meshtastic Firmware
CVE-2025-55292Same product: Meshtastic Meshtastic Firmware
CVE-2025-21608Same product: Meshtastic Meshtastic Firmware

Affected Assets

meshtastic
meshtastic firmware
2.5.0 — 2.7.15

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.1
  • V1.4.2
  • V2.1.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

SI-10 directly requires validation of information inputs, which structurally prevents type-validation failures from being introduced or exploitable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input type validation during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect type-validation flaws but does not prevent them during development.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and type checking to prevent improper type handling.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly include validation of input data types and formats.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote defensive input handling and type enforcement at system boundaries.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper type validation of all external inputs.

References