Executive Summary
AWS Security Agent, now integrated into AWS Continuum, demonstrated autonomous penetration testing capabilities by successfully exploiting 33 of 37 recently disclosed CVEs in a controlled benchmark environment. The AI-powered agent operated from minimal starting information—just endpoint URLs and single-line hints—to discover vulnerabilities, construct working exploits, and extract hidden flags across diverse software platforms including web frameworks, container registries, ML platforms, and ecommerce stacks. The 89.2% success rate spanned eight vulnerability classes from SQL injection to complex multi-step XSS-to-admin-cookie chains, with some exploits requiring sophisticated chaining of six different attack primitives. Two failures occurred when the agent's aggressive exploitation accidentally destroyed target systems before flag extraction, highlighting the critical need for non-destructive guardrails in autonomous security testing tools.
This development represents a significant advancement in AI-driven cybersecurity testing, coinciding with the rapid proliferation of AI agents across enterprise security operations and the growing sophistication of both defensive and offensive AI capabilities in 2025.
Why This Matters Now
The emergence of highly capable autonomous penetration testing agents creates both opportunities and risks as organizations increasingly rely on AI for security operations, requiring immediate attention to guardrails and ethical deployment frameworks.
Attack Path Analysis
AWS Security Agent autonomously exploited 33 of 37 recent CVEs through a six-stage attack simulation. The agent performed reconnaissance to map attack surfaces, escalated privileges through code injection and authentication bypasses, moved laterally through multi-step exploit chains, maintained command and control through various execution vectors, exfiltrated sensitive data including flags and environment variables, and caused destructive impact by taking targets offline in two cases.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Agent performed reconnaissance and discovery to map target attack surfaces, identifying vulnerable endpoints, parameters, and entry points across web frameworks, container registries, ML/AI platforms, and APIs
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Command and Scripting Interpreter
Valid Accounts
File and Directory Discovery
Remote System Discovery
Process Injection
Phishing
Exfiltration Over C2 Channel
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev 5 – Flaw Remediation
Control ID: SI-2
PCI DSS 4.0 – Application Security Testing
Control ID: 6.3.2
CISA Zero Trust Maturity Model 2.0 – Application Security
Control ID: CD.AM.1
DORA – ICT Risk Management Framework
Control ID: Article 8
NIS2 Directive – Cybersecurity Risk Management
Control ID: Article 21
ISO 27001:2022 – Use of Cryptography
Control ID: A.8.24
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Financial Services
AWS Security Agent's 89% CVE exploitation rate exposes critical vulnerabilities in payment systems, requiring enhanced Zero Trust segmentation and encrypted traffic controls.
Health Care / Life Sciences
Autonomous penetration testing reveals multi-step exploit chains threatening patient data through SQL injection and SSRF attacks requiring HIPAA compliance strengthening.
Information Technology/IT
Cloud-native security fabric vulnerabilities demonstrated across containerized environments demand immediate Kubernetes security and multicloud visibility improvements for service providers.
Government Administration
Real-world CVE exploitation capabilities against web frameworks and APIs expose critical infrastructure risks requiring enhanced threat detection and anomaly response systems.
Sources
- AWS Security Agent (now part of AWS Continuum) exploited 33 of 37 new real-world CVEshttps://aws.amazon.com/blogs/security/aws-security-agent-now-part-of-aws-continuum-exploited-33-of-37-new-real-world-cves/Verified
- AWS Security Agent (now part of AWS Continuum) exploited 33 of 37 new real-world CVEshttps://aws.amazon.com/blogs/security/aws-security-agent-now-part-aws-continuum-exploited-33-of-37-new-real-world-cves/Verified
- NIST National Vulnerability Databasehttps://nvd.nist.gov/Verified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF would likely reduce the attack scope and blast radius of this autonomous AI agent's exploitation campaign across cloud services. The segmented access controls and east-west traffic enforcement could constrain lateral movement and limit the agent's ability to chain multiple exploits across internal services.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The attack surface mapping and reconnaissance activities would likely face reduced visibility into internal cloud services and workload configurations through segmented network access controls.
Control: Zero Trust Segmentation
Mitigation: The scope of elevated privileges would likely be constrained to isolated workload boundaries rather than providing broad access across cloud services and infrastructure components.
Control: East-West Traffic Security
Mitigation: The agent's ability to pivot between internal services and chain exploits across workloads would likely be significantly constrained by east-west traffic inspection and policy enforcement.
Control: Multicloud Visibility & Control
Mitigation: The establishment and maintenance of command and control channels would likely face increased detection and potential disruption through enhanced visibility into cross-workload communications and anomalous traffic patterns.
Control: Egress Security & Policy Enforcement
Mitigation: The data exfiltration activities would likely be constrained through controlled egress policies that limit outbound data channels and enforce inspection of sensitive information leaving workload boundaries.
While some service disruption might still occur within compromised workload boundaries, the overall impact scope would likely be reduced through workload isolation and segmented access controls.
Impact at a Glance
Affected Business Functions
- Security Research and Development
- Autonomous Penetration Testing
- Vulnerability Assessment
- Cybersecurity Product Enhancement
Estimated downtime: N/A
Estimated loss: N/A
No data exposure occurred. This was a controlled security research initiative by AWS to test and validate their autonomous penetration testing agent against containerized vulnerable applications in isolated sandbox environments.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation with identity-based policies and microsegmentation to prevent lateral movement through multi-step exploit chains
- • Deploy Inline IPS with Suricata signatures to detect and block known exploit patterns and malicious payloads during the initial compromise phase
- • Establish Egress Security controls with FQDN filtering and policy enforcement to prevent data exfiltration through SSRF and other covert channels
- • Enable Multicloud Visibility & Control with centralized monitoring to detect anomalous interactions and suspicious automation patterns
- • Implement Cloud Firewall capabilities with AI-powered traffic analysis to identify and block exploit attempts before they reach vulnerable applications



