« Volver al listado

CVE-2025-55292

Estado: AnalizadaAlta (8.2)—

Meshtastic is an open source mesh networking solution. In the current Meshtastic architecture, a Node is identified by their NodeID, generated from the MAC address, rather than their public key. This aspect downgrades the security, specifically by abusing the HAM mode which doesn't use encryption. An attacker can, as such, forge a NodeInfo on behalf of a victim node advertising that the HAM mode is enabled. This, in turn, will allow the other nodes on the mesh to accept the new information and overwriting the NodeDB.

Leer descripción completaMostrar menos

The other nodes will then only be able to send direct messages to the victim by using the shared channel key instead of the PKC. Additionally, because HAM mode by design doesn't provide any confidentiality or authentication of information, the attacker could potentially also be able to change the Node details, like the full name, short code, etc. To keep the attack persistent, it is enough to regularly resend the forged NodeInfo, in particular right after the victim sends their own. A patch is available in version 2.7.6.834c3c5.

CVSS

Probabilidad de explotación (EPSS)

EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).

🎯 Técnicas ATT&CK

Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.

Red sin privilegios (AV:N/PR:N). Falsificación de NodeInfo explotando ausencia de autenticación en HAM mode para manipular NodeDB y datos de nodo; riesgo de interceptación de mensajes entre nodos.

Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.

🛡️ Mitigaciones ATT&CK que cubren estas técnicas

Network Intrusion PreventionLimit Access to Resource Over NetworkFilter Network TrafficEncrypt Sensitive InformationVulnerability ScanningUser Training

Tecnologías afectadas (1)

Meshtastic — Meshtastic Firmware

CWE

Referencias

JSON original (NVD)

Mostrar
{
  "id": "CVE-2025-55292",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-55292",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2026-01-28T15:10:33.593847Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 8.2,
          "attackVector": "NETWORK",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
          "integrityImpact": "LOW",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "NONE",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 4.2,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "meshtastic",
          "product": "firmware",
          "versions": [
            {
              "status": "affected",
              "version": "<= 2.6.2"
            }
          ]
        }
      ]
    }
  ],
  "published": "2026-01-28T00:15:49.607",
  "references": [
    {
      "url": "https://github.com/meshtastic/firmware/commit/e5e8683cdba133e726033101586c3235a8678893",
      "tags": [
        "Patch"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/meshtastic/firmware/security/advisories/GHSA-45vg-3f35-7ch2",
      "tags": [
        "Exploit",
        "Mitigation",
        "Vendor Advisory"
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-348"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Meshtastic is an open source mesh networking solution. In the current Meshtastic architecture, a Node is identified by their NodeID, generated from the MAC address, rather than their public key. This aspect downgrades the security, specifically by abusing the HAM mode which doesn't use encryption. An attacker can, as such, forge a NodeInfo on behalf of a victim node advertising that the HAM mode is enabled. This, in turn, will allow the other nodes on the mesh to accept the new information and overwriting the NodeDB. The other nodes will then only be able to send direct messages to the victim by using the shared channel key instead of the PKC. Additionally, because HAM mode by design doesn't provide any confidentiality or authentication of information, the attacker could potentially also be able to change the Node details, like the full name, short code, etc. To keep the attack persistent, it is enough to regularly resend the forged NodeInfo, in particular right after the victim sends their own. A patch is available in version 2.7.6.834c3c5."
    },
    {
      "lang": "es",
      "value": "Meshtastic es una solución de red mallada de código abierto. En la arquitectura actual de Meshtastic, un Nodo se identifica por su NodeID, generado a partir de la dirección MAC, en lugar de su clave pública. Este aspecto degrada la seguridad, específicamente al abusar del modo HAM que no utiliza cifrado. Un atacante puede, como tal, falsificar un NodeInfo en nombre de un nodo víctima anunciando que el modo HAM está habilitado. Esto, a su vez, permitirá a los otros nodos en la malla aceptar la nueva información y sobrescribir la NodeDB. Los otros nodos solo podrán entonces enviar mensajes directos a la víctima utilizando la clave de canal compartida en lugar de la PKC. Además, debido a que el modo HAM por diseño no proporciona ninguna confidencialidad o autenticación de la información, el atacante también podría potencialmente cambiar los detalles del Nodo, como el nombre completo, el código corto, etc. Para mantener el ataque persistente, es suficiente con reenviar regularmente el NodeInfo falsificado, en particular justo después de que la víctima envíe el suyo propio. Un parche está disponible en la versión 2.7.6.834c3c5."
    }
  ],
  "lastModified": "2026-06-17T09:41:35.800",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:o:meshtastic:meshtastic_firmware:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "3B2CC022-CD93-4C68-8211-93C5386E4004",
              "versionEndExcluding": "2.7.6"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}