| Version | Supported |
|---|---|
| Latest (main) | ✅ |
| Previous release | ✅ |
| < 2026.04.01 | ❌ |
If you discover a security vulnerability in Simone MCP, please:
- DO NOT open a public issue
- Email us at: security@opensin.ai
- Include the following information:
- Description of the vulnerability
- Steps to reproduce
- Potential impact assessment
- Suggested fix (if any)
We will respond within 48 hours and work with you to resolve the issue responsibly.
- Never commit OAuth tokens or JWKS keys to the repository
- Use environment variables for all sensitive configuration
- Validate
SIMONE_ALLOWED_ORIGINSfor production deployments - Set
SIMONE_OAUTH_AUDIENCEandSIMONE_OAUTH_ISSUERcorrectly
- Keep
SIMONE_AUTH_REQUIRED=truein production - Rotate OAuth credentials regularly
- Use HTTPS for all remote deployments
- Restrict access to Qdrant, Neo4j, and Supabase endpoints
- Review all dependency updates for security advisories
- Run
pytest tests/ -vbefore deploying changes - Never expose internal endpoints (Qdrant, Neo4j) publicly
- Use Docker container isolation for production deployments
- Monitor Python dependencies for known vulnerabilities
- Keep FastAPI, Python, and all libraries up to date
- Review Dockerfile base image security patches regularly
We appreciate responsible disclosure from the security community and will credit researchers who report valid security issues (with their permission).