We take security seriously. If you discover a security vulnerability in the Automated DevOps Agent, please report it responsibly.
Option 1: Private Security Advisory (Preferred)
- Go to Security Advisories
- Click "Report a vulnerability"
- Fill in the details
- Submit privately Option 2: Email
- Email: [email protected]
- Subject: "SECURITY: [Brief Description]"
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- ❌ Open public GitHub issues for security bugs
- ❌ Disclose the vulnerability publicly before we've had a chance to fix it
- ❌ Test the vulnerability on production systems
- Initial Response: Within 48 hours
- Status Update: Within 7 days
- Fix Timeline: Depends on severity (critical: < 7 days, high: < 30 days)
We currently support the following versions with security updates:
| Version | Supported | Status |
|---|---|---|
| 1.0.x | ✅ | Active |
| < 1.0 | ❌ | Deprecated |
- Arbitrary Code Execution: The debugging agent can write and run Python code
- File System Access: Agents can read/write files in the project directory
- Network Requests: The
google_search_toolmakes external HTTP requests - Shell Commands: The
shell_executor_toolruns system commands
- Run in isolated Virtual Machines (VirtualBox, VMware, etc.)
- Use Docker containers with resource limits
- Run in WSL2 with limited permissions (Windows users)
- Use Python virtual environments
- Keep git for instant rollback
- Review code before running autonomous fixes
- Set environment variable limits (e.g., max file size)
- Monitor resource usage
- Run on production servers
- Give elevated privileges (sudo/admin)
- Run on systems with sensitive data
- Allow access outside project directory
- Run on corporate networks without approval
- Execute on untrusted/unknown code
- Use your primary development machine without VM