# CVE-2026-2577: Nanobot Unauthenticated WhatsApp Session Hijack via WebSocket Bridge

> Unauthenticated remote attackers can hijack WhatsApp sessions via the default WebSocket bridge to send messages, intercept data, and capture QR codes.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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:** 16 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-3g85-xpc2-p2hq

## What is CVE-2026-2577?

CVE-2026-2577 is a critical missing authorization vulnerability in HKUDS nanobot, published on 16 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WhatsApp bridge component in Nanobot binds the WebSocket server to all network interfaces (0.0.0.0) on port 3001 by default and does not require authentication for incoming connections. An unauthenticated remote attacker with network access to the bridge can connect to the WebSocket server to hijack the WhatsApp session. This allows the attacker to send messages on behalf of the user, intercept all incoming messages and media in real-time, and capture authentication QR codes.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-2577?


## How do I fix CVE-2026-2577?

No fix has been published for CVE-2026-2577 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2577 being exploited?

There is no known exploitation of CVE-2026-2577 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2577 and fix it if it is affected.

What it is: CVE-2026-2577 is a critical missing authorization vulnerability in HKUDS nanobot, published on 16 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2577 in the wild and no public exploit code.

Affected product: HKUDS nanobot. 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-2026-2577/ (Markdown: https://insights.sbomify.com/CVE-2026-2577/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2577
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2577
- OSV: https://osv.dev/vulnerability/CVE-2026-2577

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2577/
Summaries are generated and may contain mistakes; the official description above is the record.