KoalaCast is under active development. Security fixes are applied to main,
the latest published Docker images and the latest Android release.
| Version | Supported |
|---|---|
main / latest Docker and Android releases |
✅ |
| Older tagged releases | ❌ |
Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
Instead, use one of the following private channels:
- GitHub Security Advisories (preferred) — open a private report via the repository's Security → Report a vulnerability tab.
- Email — contact the maintainer at the address listed on the GitHub profile of @Shik3i.
Please include, where possible:
- A description of the vulnerability and its impact.
- Steps to reproduce (proof-of-concept, affected endpoint, or payload).
- Affected version / commit and your environment.
- Any suggested remediation.
- Acknowledgement within 72 hours.
- An assessment and, if confirmed, a remediation plan with a target timeline.
- Credit in the release notes once a fix ships, unless you prefer to remain anonymous.
KoalaCast already ships several defensive measures relevant to reports:
- SSRF protection on all outbound feed fetches (blocks loopback, private, link-local, CGNAT, and cloud-metadata addresses; validates on redirects).
- Response-size limits on RSS bodies to guard against decompression/DoS abuse.
- Argon2id password hashing and HttpOnly, same-site session cookies.
- Rate limiting on authentication endpoints.
- Hardened container: read-only root filesystem, no capabilities,
no-new-privileges.
TLS termination and Strict-Transport-Security are the reverse proxy's job (the
reference deployment uses Caddy); the application itself does not set HSTS.
A machine-readable contact is published at /.well-known/security.txt.
Reports that strengthen or find gaps in these areas are especially valued.
Thank you for helping keep KoalaCast and its users safe.