Note: due to a packaging problem, our previous release (published and communicated earlier today/Aug 18) did not include the security fixes mentioned in the accompanying blog post for the GitLab Community Edition package. The new, just released versions of GitLab Enterprise Edition and GitLab Community Edition now contain all the necessary fixes for all versions. Please update all packages immediately. ***
Today we are releasing versions 13.2.6, 13.1.8, 13.0.14 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain important security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately.
GitLab releases patches for vulnerabilities in dedicated security releases. There are two types of security releases: a monthly, scheduled security release, released a week after the feature release (which deploys on the 22nd of each month), and ad-hoc security releases for critical vulnerabilities. You can see all of our regular and security release blog posts here. In addition, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched.
We are dedicated to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. As part of maintaining good security hygiene, it is highly recommended that all customers upgrade to the latest security release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.
Deploy Token Access Control
An authorization issue discovered in the deploy token handling allowed read access to public projects with restricted repositories. This issue is now mitigated in the latest release and is assigned CVE-2020-13296.
Thanks @ledz1996 for responsibly reporting this vulnerability to us.
Affects GitLab EE 10.7 and later.
We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible.
To update GitLab, see the update page.
Receive Security Release Notifications
To receive security release blog notifications delivered to your inbox, visit our contact us page. To receive security release blog notifications via RSS, subscribe to our RSS feed.
We want to hear from you
Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.Share your feedback