CVE-2026-35589
Nanobot ≤ 0.1.5
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:NSummary
CVE-2026-35589 is a high-severity Missing Origin Validation in WebSockets (CWE-1385) vulnerability in Nanobot Nanobot. Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as Enterprise AI Assistants; in the Privacy and Disclosure risk domain.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-35589 is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability affecting nanobot, a personal AI assistant, in versions prior to 0.1.5. The issue exists in the bridge's WebSocket server at bridge/src/server.ts and results from an incomplete remediation of CVE-2026-2577. Although the prior fix rebound the server from 0.0.0.0 to 127.0.0.1 and introduced an optional BRIDGE_TOKEN parameter, token authentication remains disabled by default, and the server does not validate the Origin header during WebSocket handshakes.
A remote attacker with no privileges can exploit this vulnerability by tricking a user into visiting a malicious website, which requires user interaction. Browsers do not enforce the Same-Origin Policy on WebSockets unless explicitly denied by the server, allowing the malicious site to connect to ws://127.0.0.1:3001/ and gain full access to the bridge API. This enables hijacking the user's WhatsApp session, reading incoming messages, stealing authentication QR codes, and sending messages on behalf of the user. The CVSS v3.1 base score is 8.0 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N), with associated CWE-1385.
The vulnerability is fixed in nanobot version 0.1.5. Mitigation involves updating to this version, as detailed in the GitHub security advisory at https://github.com/HKUDS/nanobot/security/advisories/GHSA-v5j3-4q66-58cf and release notes at https://github.com/HKUDS/nanobot/releases/tag/v0.1.5.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-22802
Vulnerability Data
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…
more
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.
- CWE(s)
AI Security AnalysisAI
- AI Category
- Enterprise AI Assistants
- Risk Domain
- Privacy and Disclosure
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: ai
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V4.4.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations on logical access, which can include origin checks before accepting WebSocket connections.
Enforces information flow policies that can require validation of communication origins at system boundaries.
Protects authenticity of communications sessions, which origin validation helps ensure for WebSocket handshakes.
Monitors and controls communications at external interfaces, directly supporting origin validation for inbound WebSocket traffic.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require origin validation for WebSocket endpoints.
Origin validation is a required step when authenticating WebSocket connection requests.
Enforcing authorization policy on incoming connections can require origin checks.
Network-level controls that block unauthorized logical access can mitigate missing origin checks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing origin validation in WebSocket implementations.
Network security controls can enforce origin validation and restrict WebSocket connections to trusted sources.
Secure configuration of network services can include origin checks for WebSocket endpoints.
Application security requirements can mandate origin validation for WebSocket communications.
Secure architecture principles can require proper origin validation mechanisms in WebSocket implementations.
Secure coding standards can explicitly require origin validation for WebSocket connections.