GitLab Security in Short
GitLab publishes security releases twice a month, more often when something is urgent, and fixes only the three newest minor versions. Self-managed instances often hold source code, CI secrets and cloud keys, so a GitLab flaw can open much more than GitLab. Account takeover and CI/CD flaws have been exploited soon after release.
How to Keep GitLab Patched
- Apply each security release promptly; GitLab marks the critical ones.
- Stay within the three newest minor versions, or you stop getting fixes.
- Turn on two-factor authentication for everyone, and limit sign-ups on public instances.
- GitLab.com is patched by GitLab; this applies to instances you run.