CVE-2026-17433 in NanoClaw
Summary
by MITRE • 07/26/2026
A vulnerability was detected in nanocoai NanoClaw up to 2.0.64. This impacts the function createChatSdkBridge.setup of the file src/channels/chat-sdk-bridge.ts of the component MCP Server Approval. Performing a manipulation results in improper authorization. The attack needs to be approached locally. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 07/26/2026
The vulnerability identified in nanocoai NanoClaw version 2.0.64 and earlier represents a critical authorization flaw within the MCP Server Approval component's chat-sdk-bridge functionality. This issue manifests specifically within the createChatSdkBridge.setup function located in src/channels/chat-sdk-bridge.ts, where improper validation allows malicious actors to manipulate the system's access controls. The vulnerability's classification aligns with CWE-285, which addresses improper authorization issues that enable unauthorized users to perform actions they should not be permitted to execute.
The attack vector requires local system access, meaning an adversary must already have compromised credentials or physical access to the target system before exploiting this weakness. This local requirement does not diminish the severity of the vulnerability, as it still provides a pathway for privilege escalation and unauthorized access to sensitive chat functionality within the MCP Server Approval framework. The fact that exploitation is now publicly documented increases the risk profile significantly, as attackers can readily implement known techniques without requiring advanced reconnaissance or sophisticated attack development.
The operational impact of this vulnerability extends beyond simple unauthorized access, potentially allowing malicious actors to manipulate chat communications, intercept sensitive data exchanges, and compromise the integrity of the messaging infrastructure. This authorization bypass could enable attackers to gain elevated privileges within the chat system, potentially leading to full system compromise if the chat bridge serves as a gateway to other critical components. The vulnerability's presence in the core messaging functionality of the MCP Server Approval system creates cascading security implications for any organization relying on this platform for secure communications.
Security practitioners should implement immediate mitigations including patching to the latest version of nanocoai NanoClaw, conducting thorough access control reviews, and implementing additional monitoring around the chat-sdk-bridge component. The vulnerability's exploitation through local manipulation aligns with ATT&CK technique T1078.004 for valid accounts and T1566.001 for spearphishing attachments, suggesting that attackers may leverage this weakness after gaining initial access through other vectors. Organizations should also consider network segmentation to limit potential lateral movement once an attacker has exploited this authorization bypass, while ensuring proper logging and monitoring capabilities are in place to detect unauthorized manipulation of the chat bridge setup function.