---
id: "GHSA-x4jf-p42g-q3hc"
kind: "vulnerability"
aliases: ["GHSA-x4jf-p42g-q3hc"]
title: "CVE-2026-112380 - Missing authorization in the WhatsApp channel in Kiro Crew"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-agent", "ai-tooling", "aws", "kiro-crew", "lab-disclosure", "self-hosted", "whatsapp"]
not_affected_if: ["default-config", "versions-0.7.2-or-later", "whatsapp-disabled"]
published_at: "2026-10-20T00:00:00+00:00"
first_seen_at: "2026-10-24T19:28:16+00:00"
updated_at: "2026-10-25T05:08:16+00:00"
sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/rss/2026-140-aws/", "first_seen_at": "2026-10-24T19:28:16+00:00"}]
---

# CVE-2026-112380 - Missing authorization in the WhatsApp channel in Kiro Crew

Kiro Crew, an open-source personal AI agent that runs tools on the operator's machine, lacks authorization checks on its WhatsApp channel and subagent run-control endpoints. In non-default configurations, a WhatsApp group member can send instructions that a subagent executes on the operator's machine, with the audit trail attributed to the operator.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Kiro Crew version; affected versions are `>=0.4.0` and `<0.7.2`.
- Inspect the Kiro Crew config for `whatsapp.groups` and confirm it has no entries.
- Confirm `whatsapp.dm_policy` is set to `self` (the default), not `open`.

## Fix

- Upgrade Kiro Crew to `0.7.2` or later.
- Patch any forked or derivative code to include the fix from PR #14338.
- Until upgraded, remove all entries from `whatsapp.groups` and keep `whatsapp.dm_policy` at `self`, or disable the WhatsApp channel.

## Timeline

- 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/

## 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_