We currently provide security updates for the following versions:
| Version | Supported |
|---|---|
| Latest | ✅ Yes |
| Previous major version | ✅ Yes |
| Older versions | ❌ No |
We take the security of OwlMail seriously. If you discover a security vulnerability, please do not report it in a public issue.
Please report security vulnerabilities by:
-
Email: Send to security@owlmail.dev
- Please use a descriptive subject line
- Include a detailed description of the vulnerability
- Provide steps to reproduce (if possible)
- Explain the potential impact
-
Wait for Response: We will acknowledge receipt within 48 hours
-
Process:
- We will assess the severity of the vulnerability
- If confirmed as a security issue, we will:
- Develop a fix
- Prepare a security advisory
- Release a patched version
- We will keep you updated on the progress
To help us better understand and fix the vulnerability, please include in your report:
- Vulnerability Type: e.g., SQL injection, XSS, privilege escalation, etc.
- Affected Component: Which feature or component is affected
- Steps to Reproduce: Detailed steps on how to reproduce the vulnerability
- Potential Impact: What consequences the vulnerability might have
- Suggested Fix (if any)
While we don't currently have a formal bug bounty program, we take security contributions seriously and will acknowledge them appropriately (with your permission).
- Keep Updated: Keep OwlMail updated to the latest version
- Network Security: Use HTTPS/TLS in production environments
- Access Control: Configure appropriate authentication and authorization
- Environment Isolation: Don't expose unprotected instances on public networks
- Sensitive Information: Don't hardcode passwords or keys in code or configuration
- Dependency Updates: Regularly update dependencies to get security patches
- Code Review: Carefully review all code changes
- Security Testing: Perform security testing during development
- Least Privilege: Follow the principle of least privilege
- Input Validation: Always validate and sanitize user input
We will disclose known security issues after they have been fixed. Check Security Advisories for details.
Security updates will be released through:
- GitHub Releases
- Security Advisories
- Project documentation updates
- Security Issues: security@owlmail.dev
- General Issues: Submit in GitHub Issues
We appreciate all researchers and users who responsibly report security issues. Your contributions help us keep OwlMail secure.