Today we are releasing versions 8.14.4, 8.13.9, and 8.12.12 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain important security fixes, and we strongly recommend that all affected GitLab installations be upgraded to one of these versions immediately.
Please read on for more details.
Security fixes in 8.14.4, 8.13.9 and 8.12.12
- CE/EE: Replace MR access checks with use of
MergeRequestsFinder
(#23867)
Security fixes in 8.14.4
- CE/EE: Destroy a user's session when they delete their account. (#25015)
- CE/EE: Filter authentication tokens from Sentry output.
- CE/EE: XSS when
LegacyDiffNote
is created on a merge request diff containing HTML (#25249) - Thanks to Kristiyan Bogdanov via HackerOne.
Other fixes in 8.14.4
- CE/EE: Fix pipeline author for Slack and use pipeline id for pipeline link (!7506)
- CE/EE: Resolve "Highlighting lines is broken" (!7090)
- CE/EE: Fix pipelines tabs (!7709)
- CE/EE: Fix compatibility with Internet Explorer 11 for merge requests (!7525)
- CE/EE: Authorize users into imported GitLab project (!7936)
- CE/EE: Remove caching of Repository#has_visible_content? (!7947)
-
CE/EE: Bump gitlab-shell version to 4.0.3 (!7953)
- EE: Prevent remote mirrors from failing when project is in pending_delete (!938)
Upgrade barometer
These versions do include a single migration, and will require brief downtime of typically less than one minute.
Please be aware that by default the Omnibus packages will stop, run migrations,
and start again, no matter how “big” or “small” the upgrade is. This behavior
can be changed by adding a /etc/gitlab/skip-auto-migrations
file.
Updating
To update, check out our update page.
Enterprise Edition
Interested in GitLab Enterprise Edition? Check out the features exclusive to EE.
Access to GitLab Enterprise Edition is included with a subscription. No time to upgrade GitLab yourself? Subscribers receive upgrade and installation services.
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