CVE & CISA-KEV Catalog

CVE-2025-53627

MEDIUM
5.3
CVSS v3
NVD

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.

How to fix

Remediation Available
meshtastic firmwareNVD
Affected:>= 2.5.0, < 2.7.15Fixed in:2.7.15CVE-2025-53627derived from NVD

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityLow
AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploit Intelligence

0.20%probability of exploitation in 30 days
10thpercentile

Low risk: more likely to be exploited than 10% of all known CVEs.

References

Exploit1

Related Vulnerabilities

Other CWE-1287 (Improper Validation of Specified Type of Input) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2024-4879Critical9.8100%KEV-
CVE-2022-31007Medium4.927%-Fix
CVE-2024-6298Critical10.019%--
CVE-2026-25639High7.52.7%-Fix
CVE-2021-43802Critical9.92.0%-Fix
CVE-2026-5946High7.51.9%-Fix

Common questions

How do I fix CVE-2025-53627?

Upgrade meshtastic firmware to 2.7.15 or later.

Is CVE-2025-53627 being actively exploited?

Not that we know of. CVE-2025-53627 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.20% is the estimated probability that it will be exploited in the next 30 days. That is higher than 10% of all scored CVEs.

How severe is CVE-2025-53627?

CVE-2025-53627 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2025-53627 affect?

Published advisories record a fix for meshtastic firmware (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2025-53627
CVE-2025-53627 severity badge

Markdown

[![CVE-2025-53627](https://tridentstack.com/cve/badge/CVE-2025-53627.svg)](https://tridentstack.com/cve/CVE-2025-53627)

HTML

<a href="https://tridentstack.com/cve/CVE-2025-53627"><img src="https://tridentstack.com/cve/badge/CVE-2025-53627.svg" alt="CVE-2025-53627"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-02-26.