Skip to main content

Kiro Crew EUVDEUVD-2026-105278

| CVE-2026-112380 CRITICAL
Missing Authorization (CWE-862)
2026-10-20 AMZN
9.0
CVSS 4.0 · Vendor: AMZN
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Join operator-configured WhatsApp group
  2. Delivery
    Send crafted control message to group
  3. Exploit
    Bypass missing authorization check
  4. Execution
    Hijack operator agent sessions
  5. Impact
    Execute 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.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Kiro Crew 0.4.0 ≤0.7.1

Affected Packages

euvd kiro_crew no fix

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

Vendor (AMZN) PRIMARY 9.0 CRITICAL
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
vuln.today AI 9.9 CRITICAL

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.

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

Primary rating from Vendor (AMZN).

CVSS VectorVendor: AMZN

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

Lifecycle Timeline

2
CVSS changed
Oct 20, 2026 - 20:22 NVD
9.9 (CRITICAL) 9.0 (CRITICAL)
CVE Published
Oct 20, 2026 - 20:05 cve.org
CRITICAL 9.0

DescriptionCVE.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

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.4%
Top 66% exploitable
Prevalence
Low
niche new Amazon AI-agent developer tool, limited production footprint
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +45
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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