CVE-2026-17433
Received Received - Intake

Improper Authorization in NanoClaw MCP Server Approval

Vulnerability report for CVE-2026-17433, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-26

Last updated on: 2026-07-26

Assigner: VulDB

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-26
Last Modified
2026-07-26
Generated
2026-07-26
AI Q&A
2026-07-26
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
nanocoai nanoclaw to 2.0.64 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-285 The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
CWE-266 A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in NanoClaw up to version 2.0.64, specifically in the createChatSdkBridge.setup function of the file src/channels/chat-sdk-bridge.ts. It involves improper authorization where a local attacker can manipulate the MCP Server Approval component by sending a forged POST request to a localhost webhook. The webhook does not authenticate the sender and trusts a manipulated user.id in the JSON body, allowing the attacker to impersonate an approver and bypass security controls.

Detection Guidance

Check if NanoClaw is running a localhost webhook on 127.0.0.1 by inspecting network connections. Use commands like 'netstat -tuln | grep 127.0.0.1' or 'ss -tuln | grep 127.0.0.1' to identify listening ports. Verify if the webhook lacks authentication by reviewing logs or configuration files for the bridge component.

Impact Analysis

An attacker with local access could exploit this to impersonate an authorized user, register unauthorized channels into agent groups, and add themselves to privileged groups. This could lead to unauthorized access to messaging platforms, data exfiltration, or manipulation of AI agents. The impact is limited to local attacks since the webhook is bound to 127.0.0.1.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data processed by AI agents, potentially violating GDPR's data protection principles or HIPAA's access controls. Unauthorized channel registrations might expose personal or health data to unauthorized parties, leading to compliance breaches and regulatory penalties.

Mitigation Strategies

Update NanoClaw to the latest version beyond 2.0.64 where the vulnerability is patched. If updating is not possible, restrict local network access to the webhook by configuring firewall rules to block unauthorized connections to the affected port.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-17433. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart