Is upgrading GitLab enough to fix CVE-2026-97229?

November 17, 2026 4 answers
Asked by 3w+socketladle_862

I saw a warning that the GitLab patch might not fully fix this vulnerability when GitLab uses a system Ruby. How can I tell whether a self-managed installation still needs work?

Answers

q.374!veltrixa

It depends on which Ruby your GitLab installation actually uses. The fix is included in GitLab's bundled packages, but a source installation or distribution package may use the operating system's Ruby instead. In that case, upgrading GitLab alone can leave the vulnerable regex engine in place.

Check the runtime used by GitLab, not just whichever Ruby appears first in your shell. The advisory identifies Ruby 3.3.13 and 3.4.12 as fixed releases, as well as 4.0.8 or later in the 4.0 series. Check your distribution's security information too, since a fix might be backported without changing to one of those upstream versions.

3w+socketladle_862:

So the Ruby version reported in my own shell isn't necessarily the one GitLab is running?

9x~ferrulebadge_318:

Right. A bundled installation can use a separate runtime, so check the installation's configuration and runtime rather than assuming they match.

Reply to this answer
q.864+brindleladle

Don't rely on an application scan alone. The source notes that Ruby did not receive a separate CVE for this flaw, so a scanner may report the GitLab issue without flagging the system Ruby that still needs the fix. Verify both components against their vendor advisories.

Reply to this answer
3k+velumratchet_715

For the GitLab side, the listed fixed releases are 19.2.8, 19.3.5 and 19.4.2. The affected ranges in the advisory are 19.2.0 through 19.2.7, 19.3.0 through 19.3.4, and 19.4.0 through 19.4.1.

This is a critical issue involving crafted regexes, with unauthenticated server-side code execution possible under conditions GitLab hasn't specified. CISA added it to its known exploited vulnerabilities catalog. Treat the GitLab and Ruby checks as urgent, not as a routine version cleanup.

Reply to this answer
Velnixa-2w

The Alpine incident is the cautionary example here. Its GitLab instance had been upgraded, but it used system Ruby, so the vulnerable engine remained. A successful GitLab upgrade by itself isn't proof that a source or distribution installation is fully remediated.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions