# CVE-2025-55292: In Meshtastic, an attacker can spoof licensed amateur flag for a node > Attackers can spoof HAM mode to bypass encryption and modify node details in Meshtastic mesh networks, requiring firmware updates. - **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 27 Jan 2026 - **Updated:** 28 Jan 2026 - **Also known as:** GHSA-45vg-3f35-7ch2 ## What is CVE-2025-55292? CVE-2025-55292 is a high-severity vulnerability in meshtastic firmware, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-348 (Use of Less Trusted Source) ## Which versions are affected by CVE-2025-55292? It affects 1 product. Products: Meshtastic Meshtastic Firmware. ## How do I fix CVE-2025-55292? No fix has been published for CVE-2025-55292 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-55292 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55292 exists. ## Other vulnerabilities in meshtastic firmware - [CVE-2025-52464](https://insights.sbomify.com/CVE-2025-52464/): Meshtastic Repeated Public and Private Keypairs (critical 9.5) - [CVE-2025-55293](https://insights.sbomify.com/CVE-2025-55293/): Meshtastic allows crafting of specific NodeInfo packets that overwrite any publicKey saved in the NodeDB (critical 9.4) - [CVE-2025-24797](https://insights.sbomify.com/CVE-2025-24797/): Meshtastic incorrectly hands malformed packets leads to controlled buffer overflow (critical 9.4) - [CVE-2024-47078](https://insights.sbomify.com/CVE-2024-47078/): Meshtastic firmware Authentication/Authorization Bypass via MQTT (high 8.1) - [CVE-2026-42566](https://insights.sbomify.com/CVE-2026-42566/): Meshtastic: Malformed UTF-8 in User.long_name broadcast over LoRa causes mesh-wide client decode failure (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-55292 and fix it if it is affected. What it is: CVE-2025-55292 is a high-severity vulnerability in meshtastic firmware, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55292 exists. Affected product: meshtastic firmware. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-55292/ (Markdown: https://insights.sbomify.com/CVE-2025-55292/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55292 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55292 - OSV: https://osv.dev/vulnerability/CVE-2025-55292 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-55292/ Summaries are generated and may contain mistakes; the official description above is the record.