# CVE-2026-17433: nanocoai NanoClaw authorization bypass in MCP Server Approval

Source: https://junglewise.ai/threats/cve-2026-17433-nanocoai-nanoclaw-authorization-bypass-in-mcp-server-approval  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-26. Updated: 2026-07-26  
License: CC BY 4.0 with a link back

CVE-2026-17433 · Severity: medium · CVSS 5.3 · Published 2026-07-26

NanoClaw, a tool used to connect messaging apps like Slack and Discord to AI agents, contains a security flaw in how it handles local approval requests. An attacker with access to the same computer where NanoClaw is running can bypass security checks to approve their own access requests by impersonating an authorized administrator. This could allow unauthorized users or malicious software on the system to gain control over agent groups and messaging channels.

## Quick answers

**Is CVE-2026-17433 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-17433 being exploited in the wild.

**How severe is CVE-2026-17433?** Medium severity, with a CVSS score of 5.3, published 26 July 2026.

**Which products and versions are affected?** nanocoai NanoClaw up to 2.0.64.

**Is there a fix for CVE-2026-17433?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-17433 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-17433?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An improper authorization vulnerability (CWE-285/CWE-266) exists in the `createChatSdkBridge.setup` function within `src/channels/chat-sdk-bridge.ts`. The application starts a local-only webhook on 127.0.0.1 to handle forwarded interaction events but fails to authenticate the sender or validate the `interaction.user.id` provided in the JSON POST body. A local unprivileged process can forge a POST request containing the ID of a legitimate approver. Because the downstream authorization check in `src/modules/permissions/index.ts` relies on this untrusted input, the attacker can successfully bypass the approval process to wire messaging groups to agent groups. As of the advisory date, the project has not responded to the issue report.

## Affected products

- nanocoai NanoClaw up to 2.0.64

## Timeline

- 2026-06-14: disclosed: Issue reported via GitHub issue #2761
- 2026-07-26: advisory: CVE published via NVD/VulDB

## References

- [https://github.com/nanocoai/nanoclaw/](https://github.com/nanocoai/nanoclaw/)
- [https://github.com/nanocoai/nanoclaw/issues/2761](https://github.com/nanocoai/nanoclaw/issues/2761)
- [https://vuldb.com/cve/CVE-2026-17433](https://vuldb.com/cve/CVE-2026-17433)
- [https://vuldb.com/submit/862450](https://vuldb.com/submit/862450)
- [https://vuldb.com/vuln/383074](https://vuldb.com/vuln/383074)
- [https://vuldb.com/vuln/383074/cti](https://vuldb.com/vuln/383074/cti)