| Version | Supported |
|---|---|
| Latest | ✅ |
| < Latest | ❌ |
Please do NOT report security vulnerabilities through public GitHub issues.
Instead, please report them through one of these channels:
- GitHub Security Advisories (preferred): Navigate to the Security tab of this repository and click "Report a vulnerability"
- Email: Send details to the maintainers listed in the repository
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
| Stage | Timeframe |
|---|---|
| Acknowledgment | Within 48 hours |
| Initial assessment | Within 7 days |
| Fix or mitigation | Within 30 days for critical/high severity |
- You'll receive an acknowledgment within 48 hours
- We'll work with you to understand and validate the issue
- We'll keep you informed of our progress
- We'll credit you in the fix (unless you prefer anonymity)
The following are in scope:
- The Mixarr application code (API and web frontend)
- Authentication and authorization mechanisms
- Data handling and storage
- Docker container configurations
- Third-party integration security
The following are out of scope:
- Vulnerabilities in upstream dependencies (report these to the dependency maintainer)
- Social engineering attacks
- Denial of service attacks that require excessive resources
- Issues in third-party services that Mixarr integrates with (Lidarr, Spotify, etc.)
- Always set a strong
SESSION_SECRETenvironment variable - Use HTTPS in production (the default Caddy configuration handles this)
- Change default database passwords before deploying
- Keep your Mixarr installation updated to the latest version
- Do not expose the API port (3005) directly — use the reverse proxy