# CVE-2026-35589: nanobot: Cross-Site WebSocket Hijacking in WhatsApp Bridge (CVE-2026-2577 Fix Update)

> Attackers can hijack WhatsApp sessions and send messages via WebSocket due to missing Origin validation in the nanobot AI assistant bridge.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-v5j3-4q66-58cf

## What is CVE-2026-35589?

CVE-2026-35589 is a high-severity vulnerability in HKUDS nanobot, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

nanobot is a personal AI assistant. Versions prior to 0.1.5 contain a Cross-Site WebSocket Hijacking (CSWSH) vulnerability exists in the bridge's WebSocket server in bridge/src/server.ts, resulting from an incomplete remediation of CVE-2026-2577. The original fix changed the binding from 0.0.0.0 to 127.0.0.1 and added an optional BRIDGE_TOKEN parameter, but token authentication is disabled by default and the server does not validate the Origin header during the WebSocket handshake. Because browsers do not enforce the Same-Origin Policy on WebSockets unless the server explicitly denies cross-origin connections, any website visited by a user running the bridge can establish a WebSocket connection to ws://127.0.0.1:3001/ and gain full access to the bridge API. This allows an attacker to hijack the WhatsApp session, read incoming messages, steal authentication QR codes, and send messages on behalf of the user. This issue has bee fixed in version 0.1.5.

Weakness: CWE-1385 (Missing Origin Validation in WebSockets)

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

It affects 1 product.


Products: Nanobot Nanobot.

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

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

## Is CVE-2026-35589 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35589 exists.

## Other vulnerabilities in HKUDS nanobot

- [CVE-2026-33654](https://insights.sbomify.com/CVE-2026-33654/): Zero-Click Indirect Prompt Injection and Authentication Bypass via Email Polling (high 8.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35589 is a high-severity vulnerability in HKUDS nanobot, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35589 exists.

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-35589/ (Markdown: https://insights.sbomify.com/CVE-2026-35589/index.md)
```

## Sources

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

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