Skip to main content

NanoClaw CVE-2026-56402

| EUVDEUVD-2026-38463 HIGH
Missing Authorization (CWE-862)
2026-06-23 VulnCheck GHSA-mhq9-hcw8-22mj
7.1
CVSS 4.0 · Vendor: VulnCheck
Share

Severity by source

Vendor (VulnCheck) PRIMARY
7.1 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vuln.today AI
6.5 MEDIUM

Network-reachable callback (AV:N), low attacker effort once a questionId is known (AC:L), requires ability to send a callback payload to the bot (PR:L), no user interaction, integrity-only impact via unauthorized approval dispatch.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

2
Source Code Evidence Fetched
Jun 23, 2026 - 16:00 vuln.today
Analysis Generated
Jun 23, 2026 - 16:00 vuln.today

DescriptionCVE.org

NanoClaw before 2.1.17 contains a privilege escalation vulnerability in the handleApprovalsResponse function that fails to verify responder role authorization. Attackers with a valid questionId can approve or reject privileged actions like package installation by submitting approval response payloads without proper role validation.

AnalysisAI

Privilege escalation in NanoClaw before 2.1.17 lets remote attackers with a valid questionId approve or reject privileged actions (such as package installation) by submitting crafted approval response payloads. The handleApprovalsResponse function dispatches sensitive handlers without verifying the responder holds an owner/admin role, turning approval callbacks into an authorization bypass. Publicly available exploit code exists via the upstream patch diff, but no active exploitation is currently confirmed.

Technical ContextAI

NanoClaw (cpe:2.3:a:nanocoai:nanoclaw) is an agent-orchestration tool that delivers approval cards to administrators over messaging platforms like Telegram and processes their button responses through handleApprovalsResponse in src/modules/approvals/response-handler.ts. The root cause is CWE-862 (Missing Authorization): the handler treats inbound callbacks as trusted simply because they carry a known questionId, never cross-referencing the responding userId against the permissions database (user-roles with owner/admin). Approval cards may be DM-delivered to admins, but the callback payload itself is untrusted input, and the missing role check allows any party who can craft or replay the callback to dispatch privileged actions like install_packages.

RemediationAI

Upgrade NanoClaw to 2.1.17 or later, which incorporates the upstream fix from commit 6227bd1a5b016fb1eb76411bb6681b4c924a51a0 (PR https://github.com/nanocoai/nanoclaw/pull/2478) that validates the responder's role against the permissions database before dispatching approval handlers. Until upgrade, restrict the messaging integration (e.g. Telegram bot) to a tightly controlled channel or DM with only trusted admin accounts, disable or avoid registering sensitive approval handlers such as install_packages, and audit pending approvals and recent privileged actions for unexpected approvers; these controls reduce exposure but do not fully close the bypass because the bug is in the server-side dispatch, not the delivery channel. Refer to the VulnCheck advisory at https://www.vulncheck.com/advisories/nanoclaw-privilege-escalation-via-unverified-approval-response-handler for further detail.

Share

CVE-2026-56402 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy