{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2025-53627","id":"CVE-2025-53627","title":"Meshtastic firmware allows forged DMs with no PKC to show up as encrypted","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 W","descriptionLong":"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.","published":"2025-12-29T16:18:29.680Z","updated":"2026-11-10T02:45:11.632686764Z","reserved":"2025-07-07T14:20:38.388Z","status":"Analyzed","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","rating":"medium","source":"GitHub_M"},"metrics":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","rating":"medium","source":"GitHub_M"},{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","rating":"medium","source":"github.com"},{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","rating":"medium","source":"OSV"}],"rating":"medium","products":["meshtastic firmware"],"affectedProducts":[{"vendor":"meshtastic","product":"firmware","defaultStatus":null,"versions":[{"version":">= 2.5, < 2.7.15","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-1287"],"aliases":["GHSA-377p-prwp-4hwf"],"references":[{"url":"https://github.com/meshtastic/firmware/security/advisories/GHSA-377p-prwp-4hwf","tags":["x_refsource_CONFIRM","Exploit","Vendor Advisory","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/53xxx/CVE-2025-53627.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-53627","tags":["advisory"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":true,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"poc","automatable":"no","technicalImpact":"partial"},"epss":0.002,"epssPercentile":0.09901,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2025-53627","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-53627","ok":true,"note":"Analyzed"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2025-53627","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2025-53627","ok":true,"note":"scored 2026-11-19"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}