GitLab· ()

This monthVendor security release

GitLab security releases: 19.5.4, 19.4.6, 19.3.8

What
GitLab published security fixes. Upgrade to 19.5.4 / 19.4.6 / 19.3.8 (whichever matches your branch). Fixes 1 CVE.
Fix
Upgrade to 19.5.419.4.619.3.8
Why this tier
Public proof-of-concept exists (SSVC exploitation: poc).
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.5.4, 19.4.6, 19.3.8.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-2026-105437:Debian · Ubuntu · Red Hat · Alpine

CVEs 1#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-105437This month7.5 (v3.1)0.4%Nopoc

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 →

Linux distribution packages#

Running the distro’s package? These are the versions that carry the fix.

Linux distribution packages CVE-2026-105437

DistroReleasePackageStatus
Debian13 trixiegitNo fix yet
12 bookwormgitNo fix yet
Ubuntu26.04 LTSgitNo fix yet
24.04 LTSgitNo fix yet
22.04 LTSgitNo fix yet
Red Hat Enterprise LinuxRHEL 10gitNo fix yet
RHEL 9gitNo fix yet
RHEL 8gitNo fix yet
RHEL 7gitNo fix yet
RHEL 6gitNo fix yet

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

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