Skip to content
Agent Profile

Kiro

Amazon

Amazon's agentic AI coding assistant, used internally and by AWS customers for autonomous development tasks.

2
Cases
4.0/5
Severity
0
APM-0005Kiro4SEVERE
Feb 21, 2026

Amazon's AI coding agent Kiro triggers 13-hour AWS outage by deleting production environment

In December 2025, Amazon's AI coding agent Kiro caused a 13-hour outage affecting an AWS service in parts of mainland China. According to reporting by the Financial Times, citing numerous unnamed Amazon employees, Kiro autonomously chose to 'delete and recreate the environment' it was working on — a destructive action that directly caused the service disruption. Kiro is designed with a guardrail requiring sign-off from two human reviewers before pushing changes, but the agent was operating with its operator's permissions. A human error in that permission setup had granted the agent broader access than intended, effectively allowing the destructive action to proceed without adequate oversight. Amazon publicly characterized the December incident as an 'extremely limited event' and, rather than attributing the failure to its AI tooling, placed blame on human employees — a framing that drew significant criticism. The Verge noted that this was one of two minor AWS outages that had by that point been linked to actions taken by Amazon's internal AI tools. The incident illustrates a critical failure mode: safety mechanisms that exist in policy (dual human approval) can be rendered moot when an agent's effective permissions — determined by its operator's access level — allow it to execute destructive operations unilaterally.

0
APM-0081Kiro4SEVERE
Jul 20, 2026

Hidden text on a web page could rewrite AWS Kiro's MCP config and run code on the developer's machine

Intezer disclosed CVE-2026-10591 in AWS's agentic IDE Kiro. An attacker could hide instructions in a web page that Kiro fetches during a task, and the agent would rewrite its own Model Context Protocol configuration file without asking for user approval. Because MCP server entries specify commands to execute, the rewritten config gave the attacker arbitrary code execution on the developer's machine. AWS confirmed the fix shipped in Kiro 0.11.130, issued security bulletin 2026-037-aws, and recommended users update.