GitLab· ()

This monthVendor security release

GitLab security releases: 19.3.1, 19.2.5, 19.1.7

What
GitLab published security fixes. Upgrade to 19.3.1 / 19.2.5 / 19.1.7 (whichever matches your branch). Fixes 7 CVEs.
Fix
Upgrade to 19.3.119.2.519.1.7
Why this tier
Vendor security release for server software (most severe: CVE-2026-18252).
Exploited
Not known to be exploited · highest EPSS 0.5%
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.3.1, 19.2.5, 19.1.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-10903 (and the other 6 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 7#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-18252Routine7.3 (v3.1)0.5%Nonone
CVE-2025-10903Routine6.5 (v3.1)0.5%Nonone
CVE-2026-77801Routine6.5 (v3.1)0.4%Nonone
CVE-2026-3035Routine5.5 (v3.1)0.3%Nonone
CVE-2026-4398Routine5.4 (v3.1)0.2%Nonone
CVE-2026-15387Routine4.3 (v3.1)0.2%Nonone
CVE-2026-7487Routine3.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.