Public Yamtrack instances raise account exposure concerns for self-hosted owners
A security-focused analysis describes Yamtrack, a self-hosted Django-based media tracker, as a product whose public instances can expose registration, social login, OpenID Connect, and personal watch history. Search counts from November 17, 2026 found 101 title matches and 135 body matches, but the author notes these figures describe pages rather than authenticated user populations. The official documentation indicates that registration is enabled by default, so owners should decide whether to disable open signup before publicizing a deployment. The analysis also flags that a sample social-login configuration requested repository permissions the tracker does not need, and recommends limiting scopes to required claims. It further advises reviewing host allowlists, CSRF trusted origins, OIDC secret storage, and account deletion and export practices, since tracker data is personal.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in