<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RADAR — GitLab patch releases</title>
    <link>https://radar.trulysovereign.com</link>
    <atom:link href="https://radar.trulysovereign.com/feeds/source/gitlab-patch-releases.xml" rel="self" type="application/rss+xml"/>
    <description>Changes RADAR detected at GitLab patch releases.</description>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 19:19:18 GMT</lastBuildDate>
    <item>
      <title>GitLab 19.6.1, 19.5.8, 19.4.10 patch CVE-2026-132825 heap overflow in Ruby</title>
      <link>https://radar.trulysovereign.com/items/4dc3d6cc-44c4-442c-9006-1100c3224920</link>
      <guid isPermaLink="false">4dc3d6cc-44c4-442c-9006-1100c3224920</guid>
      <pubDate>Sat, 21 Nov 2026 07:10:43 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/">GitLab patch releases</source>
      <description>GitLab released versions 19.6.1, 19.5.8, and 19.4.10 on November 20, 2026, patching CVE-2026-132825, a heap-based buffer overflow in Ruby's string case conversion. The vulnerability affects all GitLab CE/EE versions before 19.4.10, 19.5 before 19.5.8, and 19.6 before 19.6.1. The Ruby security team states the flaw may allow remote code execution in some scenarios. GitLab.com and GitLab Dedicated are already patched.

Why it matters: A heap overflow with potential RCE exposure is present in the Ruby runtime underlying every unpatched self-managed GitLab installation. Self-compiled installations require rebuilding Ruby with version 3.3.14 or 3.4.13, not just updating GitLab packages.

What to do: Upgrade self-managed GitLab installations to 19.6.1, 19.5.8, or 19.4.10 immediately. For self-compiled installations, rebuild the Ruby installation with Ruby 3.3.14 or 3.4.13 before or during the GitLab upgrade. Official GitLab Linux packages and container images already include the patched Ruby.</description>
    </item>
    <item>
      <title>GitLab 19.5.6, 19.4.8, 19.3.9 patch 40 security vulnerabilities including high-severity CI/CD authorization bypass</title>
      <link>https://radar.trulysovereign.com/items/fe82f0dc-26f5-4f9d-b1bf-2df40bd65a66</link>
      <guid isPermaLink="false">fe82f0dc-26f5-4f9d-b1bf-2df40bd65a66</guid>
      <pubDate>Tue, 17 Nov 2026 07:56:21 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/">GitLab patch releases</source>
      <description>GitLab released versions 19.5.6, 19.4.8, and 19.3.9 on 16 November 2026, patching 40 security vulnerabilities. Two high-severity issues (CVSS 8.7) are XSS in wiki pages (CVE-2026-105739, affects 17.2+) and error tracking (CVE-2026-108153, affects 16.1+). CVE-2026-18241 (CVSS 8.2) is a race condition in CI/CD pipeline job authorization allowing access to protected variables and resources (affects 9.3+). CVE-2026-97187 (CVSS 7.6) allows reading Kubernetes secrets from other namespaces via workspaces (affects 17.6+). Affected versions: CE/EE 19.5 before 19.5.6, 19.4 before 19.4.8, 19.3 before 19.3.9, with some vulnerabilities reaching back to version 8.0.

Why it matters: The CI/CD authorization race condition exposes protected secrets and resources to authenticated users who should not have access. The workspace vulnerability leaks Kubernetes secrets across namespace boundaries in agent-connected clusters. XSS vulnerabilities allow arbitrary JavaScript execution in authenticated users' browsers. Multiple authorization bypasses expose private repository content, job artifacts, package metadata, and CI/CD templates to unauthorized users. Self-managed installations running any affected version are exposed.

What to do: Upgrade self-managed GitLab CE/EE installations to 19.5.6, 19.4.8, or 19.3.9 immediately. GitLab.com is already patched; GitLab Dedicated requires no action. Verify your current version against the impacted ranges listed for each CVE. No migrations are included; multi-node deployments should not require downtime.</description>
    </item>
    <item>
      <title>[CORRECTED] GitLab 19.3.5 replaces broken 19.3.4 patch release</title>
      <link>https://radar.trulysovereign.com/items/1df8a326-2157-425a-bad9-595ae9641187</link>
      <guid isPermaLink="false">1df8a326-2157-425a-bad9-595ae9641187</guid>
      <pubDate>Tue, 13 Oct 2026 02:46:44 GMT</pubDate>
      <category>patch_now</category>
      <category>corrected</category>
      <source url="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/">GitLab patch releases</source>
      <description>[CORRECTED] GitLab released 19.3.5 on October 12, 2026, replacing 19.3.4 which had a bug affecting merge request pages when the Ona integration is enabled. All CVE impact statements now list 19.3.5 as the fixed version instead of 19.3.4. The release addresses 24 CVEs including CVE-2026-97229 (CVSS 10.0, unauthenticated RCE via CI/CD regex), CVE-2026-92883 (CVSS 8.7, XSS in syntax highlighting), CVE-2026-16301 (CVSS 8.5, unauthorized protected branch pipeline execution), and CVE-2026-14814 (CVSS 8.2, cache poisoning exposing CI/CD secrets).

Why it matters: If you patched to 19.3.4, merge request pages are broken for any installation using the Ona integration. If you have not patched yet, you are running a version with a critical unauthenticated remote code execution vulnerability (CVSS 10.0) that allows arbitrary code execution via a crafted CI/CD regex, plus multiple high-severity issues exposing secrets and allowing unauthorized pipeline execution.

What to do: If you are on 19.3.4 with Ona integration enabled, upgrade to 19.3.5 immediately to restore merge request functionality. If you are on any 19.3.x version before 19.3.5, upgrade to 19.3.5 to patch the critical RCE and other vulnerabilities. Self-managed installations on 19.2.x or 19.4.x should upgrade to 19.2.8 or 19.4.2 respectively.

Original text (as first published, superseded):

WHAT CHANGED: GitLab released 19.3.5 on October 12, 2026, replacing 19.3.4 which had a bug affecting merge request pages when the Ona integration is enabled. All CVE impact statements now list 19.3.5 as the fixed version instead of 19.3.4. The release addresses 26 CVEs including CVE-2026-97229 (CVSS 10.0, unauthenticated RCE via CI/CD regex), CVE-2026-92883 (CVSS 8.7, XSS in syntax highlighting), CVE-2026-16301 (CVSS 8.5, unauthorized protected branch pipeline execution), and CVE-2026-14814 (CVSS 8.2, cache poisoning exposing CI/CD secrets).</description>
    </item>
  </channel>
</rss>
