Loading vulnerability…
In Meshtastic, node identity is derived from a NodeID generated from the device MAC address rather than being bound to the node’s public key. This enables an attacker to spoof/forge a victim’s NodeInfo, specifically advertising that the victim has HAM mode enabled (a mode that does not use encryption). Other mesh nodes accept the forged NodeInfo and overwrite their NodeDB entry for the victim. As a result, peers will attempt to communicate with the victim using the shared channel key instead of public-key cryptography (PKC). Because HAM mode provides neither confidentiality nor authentication, the attacker may also be able to alter other NodeInfo fields (e.g., full name, short code). Persistence can be achieved by periodically re-sending the forged NodeInfo, especially immediately after the victim transmits its own NodeInfo. A patch is available in Meshtastic version 2.7.6.834c3c5.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.