GitLab· ()

This monthVendor security release

GitLab security releases: 19.6.1, 19.5.8, 19.4.10

What
GitLab published security fixes. Upgrade to 19.6.1 / 19.5.8 / 19.4.10 (whichever matches your branch). Fixes 1 CVE.
Fix
Upgrade to 19.6.119.5.819.4.10
Why this tier
Vendor security release for server software (most severe: CVE-2026-132825).
Exploited
Not known to be exploited · highest EPSS 0.2%
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.6.1, 19.5.8, 19.4.10.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-132825:Debian · Ubuntu · Red Hat · Alpine

CVEs 1#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-132825Routine7.4 (v3.1)0.2%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 →

Linux distribution packages#

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

Linux distribution packages CVE-2026-132825

DistroReleasePackageStatus
Debian13 trixieruby3.3No fix yet
12 bookwormruby3.1No fix yet
Ubuntu (+7 more packages)26.04 LTSruby3.3No fix yet
Red Hat Enterprise Linux (+2 more packages)RHEL 10pcsNo fix yet
RHEL 10rubyNo fix yet
RHEL 10ruby4.0No fix yet
RHEL 9pcsNo fix yet
RHEL 9rubyNo fix yet
RHEL 8pcsNo fix yet
RHEL 8rubyNo fix yet
RHEL 7pcsNo 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.