Executive Summary
In July 2026, a critical vulnerability was discovered in AWS's agentic coding IDE, Kiro. The flaw allowed hidden text on a web page to manipulate Kiro into rewriting its configuration file, leading to remote code execution on developers' machines without their approval. This security lapse was identified by Intezer in collaboration with Kodem Security. AWS has since patched the issue, though no CVE has been assigned. The vulnerability exploited Kiro's ability to autonomously modify its settings, bypassing the intended human approval process. By embedding malicious instructions in concealed text within web pages, attackers could deceive Kiro into executing arbitrary code, posing significant risks to developers and their environments. This incident underscores the growing challenges in securing AI-driven development tools. As these tools become more integrated into software development workflows, ensuring robust security measures and maintaining human oversight are paramount to prevent similar vulnerabilities.
Why This Matters Now
The rapid adoption of AI-driven development tools like Kiro introduces new security challenges. Ensuring these tools have robust safeguards and maintaining human oversight are crucial to prevent exploitation and protect development environments.
Attack Path Analysis
An attacker embedded hidden instructions in a web page, which Kiro's agentic IDE processed without user approval, leading to arbitrary code execution on the developer's machine. The attack progressed through initial compromise via hidden text, privilege escalation by modifying Kiro's configuration, lateral movement within the developer's environment, command and control through the rogue server, exfiltration of sensitive data, and potential impact on internal systems.
Kill Chain Progression
Initial Compromise
Description
The attacker embedded hidden instructions within a web page, which Kiro's agentic IDE processed when the developer requested a page summary.
Related CVEs
CVE-2026-10591
CVSS 8.8Insufficient access control restrictions in the file write tool in Amazon Kiro IDE before version 0.11 might allow remote unauthenticated actors to execute arbitrary commands via crafted instructions that cause writes to execution-sensitive paths (such as .vscode/tasks.json), enabling auto-execution on folder open.
Affected Products:
Amazon Kiro IDE – < 0.11
Exploit Status:
no public exploitCVE-2026-4295
CVSS 7.8Improper trust boundary enforcement in Amazon Kiro IDE before version 0.8.0 allowed arbitrary code execution when a user opened a maliciously crafted project directory.
Affected Products:
Amazon Kiro IDE – < 0.8.0
Exploit Status:
no public exploitCVE-2026-9255
CVSS 7.2Missing input source validation in the tool authorization prompt of Kiro CLI prior to version 1.28.0 could allow a local actor to execute arbitrary tools, including shell commands, without user approval by crafting content that is piped to kiro-cli via stdin.
Affected Products:
Amazon Kiro CLI – < 1.28.0
Exploit Status:
no public exploit
MITRE ATT&CK® Techniques
Malicious Link
Exploitation for Client Execution
System Binary Proxy Execution: Mshta
Web Shell
Exploitation of Remote Services
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Ensure all system components and software are protected from known vulnerabilities
Control ID: 6.2
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Asset Management
Control ID: 3.1
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
AWS Kiro AI/ML security flaw enables remote code execution through poisoned web pages, compromising developer environments and software development pipelines critically.
Information Technology/IT
Agentic AI coding tools vulnerability allows configuration manipulation and unauthorized code execution, threatening IT infrastructure security and development operations significantly.
Financial Services
AI-driven development tools compromise poses severe risks to financial software security, regulatory compliance, and sensitive data protection in banking environments.
Health Care / Life Sciences
Healthcare software development faces critical exposure through AI coding assistant vulnerabilities, threatening HIPAA compliance and patient data security systems.
Sources
- AWS Kiro Flaw Let a Poisoned Web Page Rewrite Its Config and Run Codehttps://thehackernews.com/2026/07/aws-kiro-flaw-let-poisoned-web-page.htmlVerified
- CVE-2026-10591 - Kiro IDE Insufficient File Write Restrictions to Execution-Sensitive Pathshttps://aws.amazon.com/security/security-bulletins/2026-037-aws/Verified
- Arbitrary code execution via crafted project files in Kiro IDEhttps://aws.amazon.com/security/security-bulletins/2026-009-AWS/Verified
- CVE-2026-9255 - Tool Execution Without Authorization via Piped Stdin in Kiro CLIhttps://aws.amazon.com/security/security-bulletins/2026-035-aws/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it would likely limit the attacker's ability to move laterally and exfiltrate data by enforcing strict segmentation and identity-based policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The attacker's ability to execute arbitrary code on the developer's machine would likely be constrained, reducing the potential for initial compromise.
Control: Zero Trust Segmentation
Mitigation: The attacker's ability to escalate privileges by modifying configuration files would likely be limited, reducing the scope of unauthorized actions.
Control: East-West Traffic Security
Mitigation: The attacker's ability to move laterally within the developer's environment would likely be constrained, reducing the risk of further system compromise.
Control: Multicloud Visibility & Control
Mitigation: The attacker's ability to establish and maintain command and control channels would likely be restricted, limiting remote command execution.
Control: Egress Security & Policy Enforcement
Mitigation: The attacker's ability to exfiltrate sensitive information would likely be limited, reducing data loss.
The attacker's potential to cause significant operational disruption would likely be reduced, limiting the overall impact of the breach.
Impact at a Glance
Affected Business Functions
- Software Development
- Code Review
- Continuous Integration/Continuous Deployment (CI/CD)
Estimated downtime: 3 days
Estimated loss: $50,000
Potential exposure of source code repositories and developer credentials.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to enforce least privilege access and prevent unauthorized configuration changes.
- • Enhance Threat Detection & Anomaly Response capabilities to identify and respond to unauthorized configuration modifications.
- • Utilize Inline IPS (Suricata) to detect and block malicious payloads embedded in web content.
- • Apply Multicloud Visibility & Control to monitor and manage interactions across cloud environments.
- • Enforce Egress Security & Policy Enforcement to control outbound traffic and prevent data exfiltration.



