| Version | Supported |
|---|---|
| 6.0.x | ✅ Active development |
| < 6.0 | ❌ End of life |
Please do NOT report security vulnerabilities through public GitHub issues.
Instead, please report them privately via email:
- Description of the vulnerability
- Steps to reproduce the issue
- Potential impact assessment
- Any suggested fix (optional but appreciated)
| Stage | Timeline |
|---|---|
| Acknowledgment | Within 48 hours |
| Initial triage | Within 7 days |
| Status update | Every 14 days until resolved |
| Fix release | Depends on severity (critical: ASAP, high: 30 days, medium: 90 days) |
We follow coordinated disclosure:
- You report the vulnerability privately
- We acknowledge and begin working on a fix
- We release the fix and publish a security advisory
- You may publish your findings after the fix is released
We will credit you in the security advisory unless you prefer to remain anonymous.
- EDDI Manager frontend application
- Authentication flows (Keycloak integration)
- API communication layer (
ApiClient) - Any XSS, CSRF, or injection vectors in the UI
- EDDI backend vulnerabilities (report to EDDI SECURITY.md)
- Third-party LLM API vulnerabilities (OpenAI, Anthropic, etc.)
- User configuration errors
- Vulnerabilities in dependencies (report upstream; we monitor via Dependabot)
- Never commit API keys, tokens, or passwords
- All user-generated content rendered via
react-markdownis sanitized with DOMPurify - Never use
dangerouslySetInnerHTMLwithout sanitization - All API calls go through
ApiClientwhich handles auth token injection