| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| < 1.0 | ❌ |
We take the security of evo-agents seriously. If you believe you have found a security vulnerability, please report it to us as described below.
Please do NOT report security vulnerabilities through public GitHub issues.
Instead, please report them via email or create a draft security advisory on GitHub.
- Report: Send an email with details about the vulnerability
- Response: We will acknowledge receipt within 48 hours
- Assessment: We will investigate and respond with our assessment
- Resolution: We will work on a fix and notify you
- Type of issue (e.g., buffer overflow, SQL injection, etc.)
- Full paths of source file(s) related to the issue
- Location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit it
We prefer all communications to be in English or Chinese.
- Keep OpenClaw Updated - Always use the latest version of OpenClaw
- Review Scripts - Review scripts before running them
- Secure Your Workspace - Keep your workspace directory private
- Don't Commit Secrets - Use
.gitignoreto exclude sensitive files - Use Private Repos - If storing sensitive data, use private Git repos
- No Secrets in Code - Never commit API keys, passwords, or tokens
- Review Dependencies - Check security of any added dependencies
- Follow Security Guidelines - Follow our security best practices
- Report Issues - Report any security concerns immediately
- The workspace is the default working directory, not a hard sandbox
- Tools resolve relative paths against the workspace
- Absolute paths can reach other host locations unless sandboxing is enabled
- Enable sandboxing for additional isolation if needed
- Memory files may contain sensitive information
- SQLite databases should be protected
- Don't commit memory files to public repositories
- Use
.gitignoreto exclude sensitive data
- Each agent has access to its workspace
- Agents can execute commands if permitted
- Review agent configurations carefully
- Use agent-specific tool restrictions when needed
We will notify users of security updates through:
- GitHub Security Advisories
- Release notes in CHANGELOG.md
- Twitter announcements (if critical)
We would like to thank the following for their contributions to our security:
- All security researchers who report vulnerabilities
- The OpenClaw community for security guidance
- Contributors who help fix security issues
For security-related questions, please contact us through GitHub or email.
Last Updated: 2026-03-26