--- id: "CVE-2026-112380" kind: "vulnerability" aliases: ["CVE-2026-112380"] title: "Kiro Crew: WhatsApp group members can run commands on the host" severity: "critical" cvss: 9.9 epss: null exploited: false status: "open" category: "ai-tooling" products: [{"name": "kirocrew", "fixed": ["0.7.2"], "affected": ">= 0.4.0, < 0.7.2", "ecosystem": "pip"}] ecosystems: ["pip"] tags: ["ai-agents", "ai-tooling", "aws", "kiro-crew", "lab-disclosure", "pip", "self-hosted", "whatsapp"] not_affected_if: ["default-config", "whatsapp-channel-disabled", "whatsapp-disabled"] published_at: "2026-10-20T00:00:00+00:00" first_seen_at: "2026-10-23T21:57:21+00:00" updated_at: "2026-10-24T19:28:16+00:00" sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112380", "first_seen_at": "2026-10-23T21:57:21+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-23T22:40:31+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-23T23:05:55+00:00"}, {"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/rss/2026-140-aws/", "first_seen_at": "2026-10-24T19:28:16+00:00"}] --- # Kiro Crew: WhatsApp group members can run commands on the host Kiro Crew (AWS open-source personal AI agent) versions 0.4.0 to 0.7.1 lack authorization checks in the WhatsApp channel and the internal subagent run-control endpoints. If the operator listed a WhatsApp group in whatsapp.groups, or set whatsapp.dm_policy to open, a member of that group can send instructions to another session's subagent. The subagent runs them on the host under that session's approval policy, and the audit log names the operator, not the sender. The default configuration is not affected. CVSS 9.9. _Summary, check and fix written by a model from the sources; labelled as such._ ## Affected - pip:kirocrew affected >= 0.4.0, < 0.7.2 fixed 0.7.2 ## How to check Run pip show kirocrew: exposed if version is >=0.4.0 and <0.7.2. Then open your Kiro Crew config: exposed only if whatsapp.groups has any entries or whatsapp.dm_policy is open. Defaults (groups empty, dm_policy self) are not exposed. Also review the audit log: actions run via this bug are attributed to the operator, not the sender. ## Fix Upgrade to kirocrew 0.7.2 (pip install -U kirocrew); also patch any forks. Workaround: remove every entry from whatsapp.groups, keep whatsapp.dm_policy at self, or disable the WhatsApp channel. ## Mitigated for you by - Team (workaround): covers Group messages from WhatsApp groups not explicitly listed in whatsapp.groups are dropped before dispatch, while dm_policy stays at self Limits: none stated Still: Remove every entry from whatsapp.groups and keep whatsapp.dm_policy at self (the default) until upgrading to 0.7.2 https://aws.amazon.com/security/security-bulletins/rss/2026-140-aws/ - Team (workaround): covers All WhatsApp channel traffic, since the channel is disabled Limits: none stated Still: Disable the WhatsApp channel until the upgrade to Kiro Crew 0.7.2 is applied https://aws.amazon.com/security/security-bulletins/rss/2026-140-aws/ ## Timeline - 2026-10-23T21:57:21+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112380 - 2026-10-23T22:40:31+00:00 analyst — Read GHSA-x4jf-p42g-q3hc and AWS bulletin 2026-140-AWS via search snippets and CVE record (full pages not fetched; v0.7.2 release page linked from CVE record, not read). Affected >=0.4.0 <0.7.2; non-default config only. No exploitation or PoC reported. No social search done. - 2026-10-23T23:05:55+00:00 analyst — Read GHSA-x4jf-p42g-q3hc in full: affected >=0.4.0 <0.7.2, fixed 0.7.2, non-default config only (whatsapp.groups non-empty or dm_policy open). Fix = per-sender allowlist on group traffic, deny by default, tool-less agent for untrusted turns, caller identity + ownership check on subagent run-control routes. v0.7.2 release notes only say 'small fix' and do not mention the CVE; the advisory is the source. No exploitation or PoC found; X chatter is only a LinuxSecurity commentary post. - 2026-10-24T19:28:16+00:00 lab https://aws.amazon.com/security/security-bulletins/rss/2026-140-aws/ — AWS: CVE-2026-112380 - Missing authorization in the WhatsApp channel in Kiro Crew ## Documents - [advisory] GHSA-x4jf-p42g-q3hc Missing authorization in the WhatsApp channel in Kiro Crew https://github.com/kirodotdev/KiroCrew/security/advisories/GHSA-x4jf-p42g-q3hc - [advisory] AWS: CVE-2026-112380 - Missing authorization in the WhatsApp channel in Kiro Crew https://aws.amazon.com/security/security-bulletins/rss/2026-140-aws/ - [discussion] LinuxSecurity on Kiro Crew flaw https://x.com/lnxsec/status/2113605614676902023 - [fix] Kiro Crew v0.7.2 release https://github.com/kirodotdev/KiroCrew/releases/tag/v0.7.2 - [mitigation] AWS bulletin 2026-140-AWS CVE-2026-112380 https://aws.amazon.com/security/security-bulletins/2026-140-aws/ ## From the sources CVE-2026-112380 - Missing authorization in the WhatsApp channel in Kiro Crew ### CVE-2026-112380 - Missing authorization in the WhatsApp channel in Kiro Crew Bulletin ID: 2026-140-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/20/2026 13:00 PM PDT Description: Kiro Crew is an open-source personal AI agent that can be reached from a web dashboard, a CLI, or messaging channels such as WhatsApp, and that runs tools on the operator's machine. We identified CVE-2026-112380, an authorization issue in the WhatsApp channel and the internal subagent run-control endpoints. In certain configurations where a WhatsApp group was added to an operator's allowed groups, or where the direct-message policy was set to open, a member of that WhatsApp group could send instructions to another session's subagent. The subagent then executed those instructions on the operator's machine under that session's approval policy, and the resulting audit trail was attributed to the operator rather than the actual sender. The default configuration is not affected: whatsapp.groups defaults to empty and whatsapp.dm_policy defaults to self, so a group that is not explicitly listed is dropped before dispatch. Impacted versions: >=0.4.0 AND <0.7.2 Resolution: This issue has been addressed in Kiro Crew version 0.7.2. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. The fix (PR #14338) makes WhatsApp group traffic subject to the same per-user allowlist as direct messages (deny by default), runs untrusted turns on a dedicated tool-less agent so the untrusted flag no longer depends on a permission prompt, and requires a verified caller identity with an ownership check on every subagent run-control route. Workarounds: Remove every entry from whatsapp.groups and keep whatsapp.dm_policy at self (the default). With no listed group, group traffic is dropped before any dispatch. Alternatively, disable the WhatsApp channel until the upgrade is applied. References: - CVE-2026-112380 - GHSA-x4jf-p42g-q3hc Please email aws-security@amazon.com with any security questions or concerns. --- _Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_