Message spoofing via silent legacy decryption fallback
Published Dec 29, 2025 · Updated Dec 29, 2025
Message spoofing in Meshtastic Firmware 2.5 through 2.7.14 allows remote attackers to inject forged direct messages via LoRa or MQTT. The receive path accepts TEXT_MESSAGE_APP packets lacking pki_encrypted by silently decrypting them with the shared AES-256-CTR channel key. Knowledge of that key, which is public on default channels, enables node impersonation because recipient interfaces do not distinguish legacy from PKI-decrypted messages.
Summary
What happened
Message spoofing in Meshtastic Firmware 2.5 through 2.7.14 allows remote attackers to inject forged direct messages via LoRa or MQTT. The receive path accepts TEXT_MESSAGE_APP packets lacking pki_encrypted by silently decrypting them with the shared AES-256-CTR channel key. Knowledge of that key, which is public on default channels, enables node impersonation because recipient interfaces do not distinguish legacy from PKI-decrypted messages.
The record
- CVE
- CVE-2025-53627
- Published
- Dec 29, 2025
- Updated
- Dec 29, 2025
- Vendor
- Meshtastic
- Product
- Meshtastic Firmware
- Classifications
- CWE-1287, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 29, 2025CVE publishedPublication date reported by the CVE source.
- Dec 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.5, < 2.7.15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor direct-message spoofing proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo