Executive Summary
In August 2026, security vulnerabilities were identified in agent infrastructures from Amazon Web Services (AWS), Google, and Vercel, allowing attackers to execute tools without model authorization. These flaws affected AWS's Bedrock AgentCore's InvokeHarness API, Google's Agent Development Kit (ADK) for Python, and Vercel's AI SDK harness packages for Codex and OpenCode coding agents. The vulnerabilities enabled untrusted instructions to reach agent tools without verification, bypassing system prompts and model-level guardrails. AWS, Google, and Vercel have since released patches to address these issues.
This incident underscores the critical need for robust input validation and authorization mechanisms in AI agent infrastructures. As AI tools become increasingly integrated into enterprise environments, ensuring their security is paramount to prevent unauthorized access and potential exploitation.
Why This Matters Now
The rapid adoption of AI agents in enterprise settings heightens the urgency to address security vulnerabilities that could lead to unauthorized tool execution and data breaches.
Attack Path Analysis
Attackers exploited vulnerabilities in AWS, Google, and Vercel agent infrastructures to execute unauthorized tool commands without model validation. This allowed them to escalate privileges, move laterally within cloud environments, establish command and control channels, exfiltrate sensitive data, and potentially disrupt services.
Kill Chain Progression
Initial Compromise
Description
Attackers exploited vulnerabilities in agent infrastructures of AWS, Google, and Vercel to inject unauthorized tool-use commands, bypassing model validation.
Related CVEs
CVE-2026-18830
CVSS 8.1Insufficient input validation in Amazon Bedrock AgentCore's InvokeHarness API allows authenticated remote users to execute tools without model authorization.
Affected Products:
Amazon Web Services Bedrock AgentCore – before July 31, 2026
Exploit Status:
no public exploitCVE-2026-18236
CVSS 9.3Google's Agent Development Kit (ADK) for Python versions before 2.5.0 allows attackers to forge tool execution approvals, leading to unauthorized tool execution.
Affected Products:
Google Agent Development Kit (ADK) for Python – before 2.5.0
Exploit Status:
no public exploitCVE-2026-64650
CVSS 6.3Vercel's @ai-sdk/harness-codex versions up to 1.0.28 allow untrusted code within a Linux sandbox to execute host-exposed tools without model authorization.
Affected Products:
Vercel @ai-sdk/harness-codex – up to 1.0.28
Exploit Status:
no public exploitCVE-2026-64651
CVSS 6.3Vercel's @ai-sdk/harness-opencode versions up to 1.0.27 allow untrusted code within a Linux sandbox to execute host-exposed tools without model authorization.
Affected Products:
Vercel @ai-sdk/harness-opencode – up to 1.0.27
Exploit Status:
no public exploit
MITRE ATT&CK® Techniques
Compromise Infrastructure: Serverless
Resource Hijacking: Cloud Service Hijacking
Remote Services: Cloud Services
Cloud Administration Command
Cloud Infrastructure Discovery
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Change Control Processes
Control ID: 6.4.1
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Data
Control ID: Pillar 3
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
AI agent vulnerabilities in AWS, Google, and Vercel platforms expose software development pipelines to unauthorized tool execution and credential exfiltration attacks.
Information Technology/IT
Supply-chain compromise through agent infrastructure flaws enables attackers to bypass model guardrails and execute malicious tools without proper authorization validation.
Computer/Network Security
Security infrastructure utilizing AI agents faces critical authorization bypass risks allowing direct tool invocation without model verification or content filtering protection.
Financial Services
Banking systems using AI agents for automation face severe compliance violations and unauthorized access risks through CVE-2026-18830 and related agent vulnerabilities.
Sources
- AWS, Google, and Vercel Agent Flaws Let Attackers Trigger Tools Without Running the Modelhttps://thehackernews.com/2026/08/aws-google-and-vercel-patch-agent-flaws.htmlVerified
- CVE-2026-18830 - Issue with Amazon Bedrock AgentCore harness – Insufficient Input Validationhttps://aws.amazon.com/security/security-bulletins/2026-073-aws/Verified
- CVE-2026-18236 Detailhttps://nvd.nist.gov/vuln/detail/CVE-2026-18236Verified
- Security Advisory: CVE-2026-64650https://github.com/vercel/ai/security/advisories/GHSA-qw9h-448j-6rphVerified
- Security Advisory: CVE-2026-64651https://github.com/vercel/ai/security/advisories/GHSA-g48p-5rr5-8rgqVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it could have constrained the attacker's ability to exploit vulnerabilities, escalate privileges, and move laterally within cloud environments, thereby reducing the potential blast radius.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The attacker's ability to exploit vulnerabilities in agent infrastructures may have been limited, reducing the likelihood of unauthorized command execution.
Control: Zero Trust Segmentation
Mitigation: The attacker's ability to escalate privileges within the cloud environment could have been constrained, limiting their access to sensitive resources.
Control: East-West Traffic Security
Mitigation: The attacker's lateral movement across cloud services and resources would likely have been limited, reducing the potential spread of the attack.
Control: Multicloud Visibility & Control
Mitigation: The establishment of command and control channels by attackers may have been constrained, limiting their ability to maintain persistent access.
Control: Egress Security & Policy Enforcement
Mitigation: The exfiltration of sensitive data to external destinations would likely have been limited, reducing the risk of data breaches.
The overall impact of the attack, including service disruptions and data compromise, may have been reduced, limiting the extent of damage.
Impact at a Glance
Affected Business Functions
- AI Model Deployment
- Software Development
- Cloud Infrastructure Management
Estimated downtime: 3 days
Estimated loss: $500,000
Potential unauthorized access to sensitive tools and data managed by AI agents.
Recommended Actions
Key Takeaways & Next Steps
- • Implement strict input validation to prevent unauthorized tool execution.
- • Enforce zero trust segmentation to limit lateral movement within cloud environments.
- • Enhance egress security policies to detect and prevent unauthorized data exfiltration.
- • Deploy anomaly detection systems to identify and respond to unusual activities.
- • Regularly audit and update security controls to address emerging vulnerabilities.



