Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessJoin operator-configured WhatsApp group
-
DeliverySend crafted control message to group
-
ExploitBypass missing authorization check
-
ExecutionHijack operator agent sessions
-
ImpactExecute arbitrary commands on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the operator has enabled and configured the WhatsApp group channel integration in Kiro Crew, and that the attacker is an existing member of that specific operator-configured WhatsApp group (reflected as AT:P and PR:L in the CVSS vector). It does not require any user interaction from the operator (UI:N) and is performed remotely over the network by sending messages to the group. Limiting factors: deployments that do not use the WhatsApp group integration are not exposed, and the attacker must first obtain membership in the target group, so the realistic attacker population is restricted to current or past group members or anyone who can compromise a member's WhatsApp account. |
| Impact | This is a genuine high-priority issue despite several missing exploitation signals. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:L/UI:N) with full high impact to both the vulnerable system (VC:H/VI:H/VA:H) and subsequent systems (SC:H/SI:H/SA:H) yields a 9.0 Critical, driven by arbitrary command execution on the host - a worst-case technical impact. The key limiting signal is AT:P combined with PR:L: exploitation is not open to any anonymous internet actor but requires the attacker to already be a member of an operator-configured WhatsApp group, which is a meaningful barrier and argues against mass, automatable exploitation. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no evidence of active or widespread exploitation at this time - the risk is driven by impact severity and the plausibility of a malicious or compromised group member, not by observed in-the-wild activity. The signals are internally consistent (network vector, low added complexity, a specific precondition), with no contradiction between the vector and the description. Treat this as a prioritize-and-patch item for anyone running Kiro Crew with WhatsApp group integration, while recognizing the attack-requirement precondition narrows the realistic attacker population. |
| Exploit ScenarioDerived | An operator configures Kiro Crew to take instructions from a WhatsApp group and adds several people to that group. A member of the group (or someone who gains access to a member's account) sends a crafted message that the missing-authorization flaw treats as a privileged command, letting them hijack the operator's other agent sessions and run arbitrary shell commands on the host. No public exploit code was identified at time of analysis, but the attack requires only sending messages to a group the attacker already belongs to. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 20, 2026
Kiro Crew before version 0.7.2 contains a missing authorization flaw in its WhatsApp group channel integration that lets a remote attacker who is a member of an operator-configured WhatsApp group control the operator's other agent sessions and execute arbitrary commands on the host. The attacker must already belong to the specific group (low privileges, PR:L), but no operator interaction is required; deployments that do not enable the WhatsApp channel are not exposed. The vendor has released version 0.7.2 to fix the issue, and no public exploit code has been identified at the time of analysis.
RemediationAI
Upgrade Kiro Crew to version 0.7.2, which is the vendor-released patch (see https://github.com/kirodotdev/KiroCrew/releases/tag/v0.7.2 and the AWS bulletin https://aws.amazon.com/security/security-bulletins/2026-140-aws/). If immediate upgrade is not possible, disable the WhatsApp group channel integration; this removes the exposed functionality but also eliminates the attack vector. As a further compensating control, restrict the operator-configured WhatsApp group to the smallest possible membership and remove any untrusted or former participants, recognizing that any current member can still exploit the flaw. After upgrading, review agent session activity and host command logs for signs of unauthorized use associated with the WhatsApp channel, and rotate any credentials or tokens accessible to affected agent sessions.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is classified as CWE-862 Missing Authorization. Kiro Crew's WhatsApp group channel integration accepts messages from group members and, without an adequate authorization check, uses them to drive other agent sessions and run commands on the underlying host. The CVSS 4.0 vector AV:N/AC:L/AT:P/PR:L/UI:N with high confidentiality, integrity, and availability impact on both the vulnerable system and subsequent systems reflects that exploitation requires the WhatsApp integration to be enabled and the attacker to be a member of the operator-configured group (AT:P), while requiring only low privileges (PR:L) and no user interaction (UI:N). The CPE cpe:2.3:a:amazon:kiro_crew:*:*:*:*:*:*:*:* identifies Amazon Kiro Crew as the affected product; the vendor advisory specifies version 0.7.2 as the fixed release.
Know when Kiro Crew gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Network-delivered via group messages (AV:N); group membership is a low-privilege precondition (PR:L); no operator interaction (UI:N); command execution breaks out to the host and other sessions, so scope changes (S:C) with full C/I/A impact.
Primary rating from Vendor (AMZN).
CVSS VectorVendor: AMZN
Lifecycle Timeline
2DescriptionCVE.org
Missing authorization in the WhatsApp group channel in Kiro Crew might allow a remote actor who is a member of an operator-configured WhatsApp group to control the operator's other agent sessions and execute arbitrary commands on the host running Kiro Crew via messages sent to the group.
To remediate this issue, users should upgrade to version 0.7.2.
Technical POC Analysis
The flaw is missing authorization, CWE-862.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Kiro Crew versions prior to 0.7.2 contain a critical missing authorization flaw in the optional WhatsApp group channel integration that allows an authenticated low-privilege member of an operator-configured group to control other agent sessions and execute arbitrary commands on the host. Organizations that have enabled the WhatsApp channel are exposed to unauthorized host-level actions by any member of that group, creating insider and third-party risk even though no public exploit code has been identified at time of analysis. Leadership should prioritize patching to 0.7.2 and reviewing who belongs to these groups because the flaw turns group membership into a command-execution path.
Apply vendor patch (Vendor-released patch: 0.7.2). If immediate patching is not possible, disable the WhatsApp channel integration and restrict operator-configured group membership to trusted users only.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-105278
NVD
CVE.org
EPSS
GitHub
VulDB
Exploit-DB