| Version | Supported |
|---|---|
| 0.5.x | ✅ |
| < 0.5 | ❌ |
We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.
- Do NOT create a public GitHub issue for security vulnerabilities
- Email security concerns to: [email protected]
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested fixes (optional)
- Acknowledgment: Within 48 hours of your report
- Initial Assessment: Within 5 business days
- Resolution Timeline: Depends on severity
- Critical: 24-48 hours
- High: 1 week
- Medium: 2 weeks
- Low: Next release cycle
This security policy applies to:
- The
iris-vector-ragPython package - Associated Docker images
- API endpoints when deployed
- MCP server implementations
- Vulnerabilities in dependencies (report to upstream maintainers)
- Issues in user-deployed configurations
- Social engineering attacks
When using iris-vector-rag:
- API Keys: Never commit API keys or credentials to version control
- Database Credentials: Use environment variables for IRIS connection strings
- Docker: Run containers as non-root users in production
- Network: Use TLS for all production API communications
- Updates: Keep dependencies updated with
uv sync --upgrade
iris-vector-rag includes:
- Parameterized SQL queries (SQL injection prevention)
- Input validation on all API endpoints
- Rate limiting support
- Audit logging capabilities
- RBAC policy interface
We appreciate responsible disclosure and will acknowledge security researchers who help improve our security.