GitLab· ()

This monthVendor security release

GitLab security releases: 18.6.2, 18.5.4, 18.4.6

What
GitLab published security fixes. Upgrade to 18.6.2 / 18.5.4 / 18.4.6 (whichever matches your branch). Fixes 10 CVEs.
Fix
Upgrade to 18.6.218.5.418.4.6
Why this tier
Vendor security release for server software (most severe: CVE-2025-12716).
Exploited
Not known to be exploited · highest EPSS 0.9%
Share this

What to do now#

  1. Check whether you run an affected GitLab version:
    sudo gitlab-rake gitlab:env:info | grep -A2 GitLab
  2. Upgrade to the fixed release for your branch: 18.6.2, 18.5.4, 18.4.6.Vendor announcement
  3. Self-managed only (GitLab.com is patched by GitLab). Follow the upgrade path: you may need intermediate versions.
  4. Using distro packages? Distros backport fixes under their own version numbers. Check your distro's status for CVE-2025-11247 (and the other 9 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 10#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2025-12716Routine8.7 (v3.1)0.4%Nonone
CVE-2025-12029Routine8.0 (v3.1)0.5%Nonone
CVE-2025-8405Routine7.7 (v3.1)0.5%Nonone
CVE-2025-12562Routine7.5 (v3.1)0.9%Nonone
CVE-2025-11984Routine6.8 (v3.1)0.4%Nonone
CVE-2025-14157Routine6.5 (v3.1)0.3%Nonone
CVE-2025-4097Routine6.5 (v3.1)0.3%Nonone
CVE-2025-11247Routine4.3 (v3.1)0.3%Nonone
CVE-2025-13978Routine4.3 (v3.1)0.3%Nonone
CVE-2025-12734Routine3.5 (v3.1)0.3%Nonone

Sources#

Built from GitLab: about.gitlab.com security feed, checked . Tier from the published rubric.

Also on today's list

See today's list → · Coming up →

Something wrong on this page?
Anonymous. Reports are checked against the primary source.