Message forgery via unchecked PKC receipt state
Published Jun 24, 2025 · Updated Jun 24, 2025
Improper input validation in Meshtastic-Android before 2.5.21 allows remote attackers to forge direct messages that appear PKC-protected. The message-processing path associates a shared-channel-key DM with the impersonated node's PKC chat and renders the green padlock without verifying PKC receipt. Mesh access is sufficient to inject trusted-looking content; the demonstrated consequence is message-integrity loss, not data disclosure or service interruption.
Summary
What happened
Improper input validation in Meshtastic-Android before 2.5.21 allows remote attackers to forge direct messages that appear PKC-protected. The message-processing path associates a shared-channel-key DM with the impersonated node's PKC chat and renders the green padlock without verifying PKC receipt. Mesh access is sufficient to inject trusted-looking content; the demonstrated consequence is message-integrity loss, not data disclosure or service interruption.
The record
- CVE
- CVE-2025-52883
- Published
- Jun 24, 2025
- Updated
- Jun 24, 2025
- Vendor
- Meshtastic
- Product
- Meshtastic-Android
- Classifications
- CWE-1287, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2025CVE publishedPublication date reported by the CVE source.
- Jun 24, 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.21
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
- Experimental forged-DM reproductionproof 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