Security fixes are applied on the current main branch and published in the next host release. Older tags are not backported unless a release note says otherwise.
| Version | Supported |
|---|---|
| Latest GitHub Release on krate-apps/fleet | Yes |
| Older tags / forks | No (please upgrade) |
Do not open a public GitHub issue for security-sensitive findings (RCE, auth bypass, SSRF, secret leakage, privilege escalation, etc.).
Prefer one of:
- GitHub private vulnerability reporting on this repository (preferred when enabled).
- A private message to the maintainers via the Krate contact channels, with a clear subject such as
Fleet security report.
Please include:
- Affected version / commit (or “built from main at <sha>”)
- Impact and attack prerequisites (auth required? local-only? reverse proxy?)
- Reproduction steps or a minimal proof of concept
- Whether you are already coordinating disclosure elsewhere
We aim to acknowledge reports within a few business days and to ship a fix or mitigation before any coordinated public write-up.
Fleet is a self-hosted multi-client BitTorrent UI (qBittorrent, Deluge, Transmission, rTorrent). Treat the host, reverse proxy, and client APIs as part of the trust boundary.
- Bind to loopback by default; put TLS termination in a reverse proxy (Reverse proxy).
- Keep
auth.disable: falseexcept for local debugging on loopback (Fleet refusesauth.disableon non-loopback listen addresses). - Set
auth.secure_cookies: truebehind HTTPS (Fleet also setsSecurewhenX-Forwarded-Proto: https). - Configure
security.process_exec_allowlist/process_exec_dirsbefore any extension may useprocess.exec(fail-closed when empty). - Authenticate extension webhooks with
Authorization: BearerorX-Api-Keyonly — the token must not appear in the URL (Hooks). - Keep
data_dirpermissions tight; gateway passwords areenc:v1:AES-GCM. The master key is resolved from systemdCREDENTIALS_DIRECTORY/fleet-secrets.key, then the Linux user keyring (fleet-secrets), thendata_dir/.fleet-secrets.key(0600). PreferLoadCredential=on the unit when possible. - Pin catalogue installs with
sha256hashes; do not install unsigned archives from untrusted buckets.
- Install · Reverse proxy · SDK · Hooks
- Contributing