{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "versions": [
              {
                "introduced": "2.5"
              },
              {
                "fixed": "2.7.15"
              }
            ]
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "d18f3f7a658817b35a3ab746d8522c1136890785"
            }
          ],
          "repo": "https://github.com/meshtastic/firmware",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-377p-prwp-4hwf"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-1287"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/53xxx/CVE-2025-53627.json"
  },
  "details": "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.",
  "id": "CVE-2025-53627",
  "modified": "2026-04-01T23:10:08.267664642Z",
  "published": "2025-12-29T16:18:29.680Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/53xxx/CVE-2025-53627.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/meshtastic/firmware/security/advisories/GHSA-377p-prwp-4hwf"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-53627"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Meshtastic firmware allows forged DMs with no PKC to show up as encrypted"
}