# Security policy ## Supported versions Security fixes are made for the latest release only. Upgrade before reporting a problem you found in an older version; the in-app update check (Settings › Updates) and `docker compose pull` keep installations current. | Version | Supported | |---|---| | Latest release | Yes | | Older releases, pre-releases, `:nightly` images | No | ## Reporting a vulnerability Please **do not open a public issue** for a security problem. Gitea has no private vulnerability reporting: report the problem privately to the maintainers, through the contact on the repository owner's Gitea profile or by e-mail to them. Include: - the affected program (Chronos, Uploader, Server) and version (Settings › About, or `/api/v1/server/info` for the server); - how to reproduce the problem, and what an attacker gains; - whether the server runs behind a reverse proxy and which TLS mode it uses (`auto`, `pem`, `proxy`). Do not attach diagnostics bundles or logs that you have not read: they are scrubbed of passwords and tokens, but they contain host names, folder paths and user names. You will receive an acknowledgement within 7 days. Fixes are released as soon as they are ready, and the release notes credit the reporter unless they prefer otherwise. Please give us 90 days, or until a fix is released, before disclosing the problem publicly. ## Scope In scope: the desktop programs, the installer, the server API and admin panel, the Docker image and the Unraid template published here. Out of scope: problems that need an attacker who already controls the user's Windows account or the server host; denial of service through unrealistic load; self-signed certificate warnings (the client pins the fingerprint you confirm at first connection); findings from automated scanners without a demonstrated impact. ## How Chronos protects you - Releases list the SHA-256 of every file in `SHA256SUMS`; the in-app update download refuses a file whose hash does not match. Builds are Authenticode-signed when a signing certificate is configured. - The server stores passwords with PBKDF2-SHA512 (210,000 iterations) and session tokens only as SHA-256 hashes; sign-in is rate limited and accounts lock after repeated failures. - Desktop clients pin the server certificate fingerprint on first use, never send a saved token to a server whose certificate changed, and keep tokens encrypted with Windows DPAPI. - No program runs external tools or scripts; the only programs Chronos starts are your browser (for links) and Explorer (to show a folder).