Unauthenticated WhatsApp Session Hijacking in Nanobot WhatsApp Bridge
CVE-2026-2577 is a missing-authentication vulnerability in the WhatsApp bridge component of Nanobot. The bridge exposes a WebSocket server that, by default, binds to all network interfaces (0.0.0.0) on TCP port 3001 and does not require authentication for incoming connections. As a result, any unauthenticated remote attacker with network reachability to the exposed bridge can connect directly to the WebSocket service and interact with the bridge API, leading to hijacking of the victim’s WhatsApp session. The issue affects exposed Nanobot instances and was reported by Tenable. Supporting content maps the weakness to CWE-306 and indicates the issue was fixed by the project in a later release.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An earlier vulnerability in nanobot whose remediation was incomplete, leading to a subsequent CSWSH issue in the bridge WebSocket server.
An authentication-missing exposure in Nanobot’s WhatsApp bridge WebSocket service (bound to 0.0.0.0:3001 by default) that allows unauthenticated remote session hijacking, message interception, and QR code capture.
A max-severity vulnerability in the nanobot personal AI assistant that could allow remote attackers to hijack WhatsApp sessions when nanobot instances are exposed.
The version that knows your environment.
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.