GitLab· ()

This monthVendor security release

GitLab security releases: 19.1.2, 19.0.4, 18.11.7

What
GitLab published security fixes. Upgrade to 19.1.2 / 19.0.4 / 18.11.7 (whichever matches your branch). Fixes 8 CVEs.
Fix
Upgrade to 19.1.219.0.418.11.7
Why this tier
Vendor security release for server software (most severe: CVE-2026-6896).
Exploited
Not known to be exploited · highest EPSS 0.4%
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: 19.1.2, 19.0.4, 18.11.7.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-12506 (and the other 7 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 8#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-6896Routine8.7 (v3.1)0.4%Nonone
CVE-2026-13320Routine7.3 (v3.1)0.4%Nonone
CVE-2026-11827Routine4.9 (v3.1)0.4%Nonone
CVE-2026-7492Routine4.3 (v3.1)0.3%Nonone
CVE-2026-8472Routine4.3 (v3.1)0.4%Nonone
CVE-2025-12506Routine3.5 (v3.1)0.3%Nonone
CVE-2026-6352Routine2.7 (v3.1)0.4%Nonone
CVE-2026-13151Routine——No—

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.