| Version | Supported |
|---|---|
| 0.6.x | ✅ Current release |
| 0.5.x | |
| < 0.5 | ❌ Unsupported |
We take security seriously. If you discover a security vulnerability in AgenticFleet, please report it responsibly.
- Do NOT open a public GitHub issue for security vulnerabilities.
- GitHub Security Advisories: Use GitHub's private vulnerability reporting (preferred).
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact assessment
- Any suggested fixes (optional)
- Acknowledgment: Within 48 hours of your report
- Initial Assessment: Within 5 business days
- Status Updates: Every 7 days until resolution
- Resolution Timeline: Typically 30-90 days depending on severity
| Severity | Description | Target Resolution |
|---|---|---|
| Critical | Remote code execution, data breach | 7 days |
| High | Authentication bypass, privilege escalation | 14 days |
| Medium | Information disclosure, denial of service | 30 days |
| Low | Minor issues, hardening recommendations | 90 days |
We consider security research conducted in good faith to be authorized. We will not pursue legal action against researchers who:
- Make a good faith effort to avoid privacy violations and data destruction
- Only interact with accounts they own or have explicit permission to test
- Do not exploit vulnerabilities beyond demonstrating the issue
- Report findings promptly and provide reasonable time for remediation
- Store
OPENAI_API_KEY,TAVILY_API_KEY, and other secrets in environment variables - Never commit
.envfiles or secrets to version control - Use separate API keys for development and production
- Rotate keys periodically and immediately if compromised
- Run behind a reverse proxy (nginx, Caddy) with TLS termination
- Enable CORS restrictions for production (
CORS_ALLOWED_ORIGINS) - Use network segmentation to limit API exposure
- Monitor logs for suspicious activity
- The
/api/ws/chatendpoint validates connection origins againstCORS_ALLOWED_ORIGINS - Localhost connections are allowed by default for development (
WS_ALLOW_LOCALHOST=true) - For production, set
CORS_ALLOWED_ORIGINSexplicitly and consider settingWS_ALLOW_LOCALHOST=false - Set appropriate rate limits to prevent abuse (
MAX_CONCURRENT_WORKFLOWS)
We use automated tools to monitor dependencies:
- Bandit: Static analysis for Python security issues (CI pipeline)
- npm audit: JavaScript dependency scanning
To check locally:
# Python
uv run bandit -r src/agentic_fleet
# JavaScript
cd src/frontend && npm auditSecurity patches are released as soon as possible after a vulnerability is confirmed. Subscribe to GitHub releases to be notified of security updates.