CVE-2026-132825: Ruby Heap Overflow Forces a GitLab Critical Patch Release

GitLab shipped a critical patch release on November 20 for CVE-2026-132825, a one-byte heap overflow in Ruby's string case conversion. The Ruby team and GitLab call it Critical, MITRE scores it 7.4 High, and no exploitation has been reported.

CVE-2026-132825: Ruby Heap Overflow Forces a GitLab Critical Patch Release

GitLab shipped a critical patch release on November 20 (19.6.1, 19.5.8 and 19.4.10) to fix CVE-2026-132825, a heap-based buffer overflow in Ruby's string case conversion. The flaw is in Ruby itself, so any application on an affected Ruby is in scope, but GitLab is the product that made it urgent for many teams.

The CVE is not in CISA's KEV catalog, and none of the sources we read report exploitation in the wild. What is public is a claim of reach: the Ruby team says it is aware of proof-of-concept code that triggers remote code execution in some scenarios, while a third-party analysis says its own PoC is still a week out.

How the bug works

When Ruby changes the case of a string in some single-byte encodings, such as ISO-8859-1 and Windows-1252, it can write one byte past the end of the output buffer. The CVE record says: "One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252." MITRE classifies it as CWE-122, a heap-based buffer overflow.

A write-up by Veria Labs traces it to the German sharp s. Uppercasing ß produces two bytes (SS), but the loop checks for room for only one. Veria Labs says the same loop exists in several ISO-8859 and Windows-125x encodings, dates back to Ruby 2.4.0, and that UTF-8 strings take a different path and are not affected. It names upcase, swapcase, downcase(:fold) and casecmp? as the affected operations. That detail comes from this one analysis; the Ruby advisory does not list methods.

The Ruby advisory says changing the case of a crafted string "may allow remote code execution," and the GitHub advisory adds that the Ruby team is aware of PoCs that prove it "in some scenarios." The issue was reported by Stephan Lipp (Ada Logics) and Anthropic.

Who is affected

Product

Affected

Fixed in

Ruby 3.3

up to 3.3.13

3.3.14

Ruby 3.4

3.4.0 to 3.4.12

3.4.13

Ruby 4.0

4.0.0 to 4.0.9

4.0.10

GitLab CE/EE 19.4

before 19.4.10

19.4.10

GitLab CE/EE 19.5

before 19.5.8

19.5.8

GitLab CE/EE 19.6

before 19.6.1

19.6.1

GitLab.com is already patched. GitLab Dedicated was covered by internal-only releases 19.5.7 and 19.4.9 with interim mitigations. Self-managed instances have to upgrade, and self-compiled installs have to rebuild Ruby with 3.3.14 or 3.4.13.

Ruby 3.2 and earlier are end of life and will not receive these fixes, according to the Ruby advisory. The CVE record's affected range for the 3.3 line starts at version 0, so older releases fall inside it.

The Ruby advisory covers seven vulnerabilities in Regexp and String, and GitLab's fix covers the others too. CVE-2026-132825 is the CVE the MITRE record ties to GHSA-34m4-m9fh-gqp5, the case conversion bug. We found no CVE IDs for the other six in the sources we read.

Distribution packages are a separate question. Ubuntu rates the CVE Medium and lists no fixed package for any release; several Ruby packages are marked "Needs evaluation" and others "Not in release." The SUSE bug page could not be read because it sits behind a bot challenge.

One flaw, three ratings

This CVE is a good example of why a single severity word can mislead. Every source below describes the same bug.

Source

Rating

Detail

Ruby team (GHSA)

Critical

No score or vector shown

GitLab release page

Critical

Says it reflects the Ruby team's rating

MITRE (CVE record)

7.4 High

CVSS 3.1, AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Ubuntu

Medium

Priority only, no CVSS

CISA SSVC

No known exploit

Not automatable, total technical impact

EPSS (VulnTracker)

0.2%

Chance of exploitation in the next 30 days

The MITRE vector explains the gap with the Critical label. It scores the attack vector as Local and the complexity as High, because the bug sits in a library function. The Ruby team and Veria Labs look at it from the application side: if an app lets untrusted text in a legacy encoding reach case conversion, the path can be remote. Veria Labs claims this holds for default Rails and classic Sinatra setups, but its PoC is unpublished, so that reach is a claim, not a demonstrated result. The score depends on which of those two views you take.

The response was fast. The Ruby advisory was posted on November 18 (its page history says 19 November 00:00 UTC), the CVE was published on November 19 at 06:34 UTC, and GitLab shipped its patch release on November 20.

Reading it on VulnTracker

The CVE page shows CVSS 7.4 High, which is the MITRE score. The Critical rating comes from the Ruby team and GitLab and does not appear as a number anywhere we looked, so a 7.4 on the page is not a contradiction of GitLab's label.

EPSS is 0.2%. SSVC reads No known exploit, Not automatable, Total impact, and the status is Received, meaning NVD has not analysed the entry yet. The weakness is CWE-122. The entry was published on November 19 at 06:34 UTC and updated on November 20 at 05:18 UTC, and CERT-Bund tracks it as WID-SEC-W-2026-4668 (High, November 19, 4 affected products).

The Exploits tab lists 3 entries. We did not review them, so we cannot say what they contain. SSVC still says no known exploit, and none of the sources we read report exploitation in the wild.

Two data notes. The GitHub advisory page we read still says "No known CVE" and lists CWE-193 (off-by-one), while the MITRE record is published and uses CWE-122. The page we read looks older than the CVE link. And the Veria Labs analysis refers to the flaw by its GHSA ID and "CVE pending," so it does not confirm the CVE number by itself.

What to do

  1. Upgrade self-managed GitLab to 19.6.1, 19.5.8 or 19.4.10, whichever matches your branch. GitLab says there are no new migrations and multi-node installs should not need downtime.
  2. If you compile GitLab yourself, rebuild it with Ruby 3.3.14 or 3.4.13, as GitLab's notes say.
  3. Look for other Ruby on your hosts. Move to 4.0.10, 3.4.13 or 3.3.14, and plan a migration off 3.2 and earlier, which get no fix.
  4. Check your distribution's package status. Ubuntu lists no fixed package yet.
  5. Do not count on a workaround. The Ruby advisory names none and says to upgrade.

Takeaway

Patch GitLab first, then find the other Ruby on your hosts. The spread between Critical, 7.4 High and Medium is a reminder to read the reasoning behind a score instead of the label. Follow this CVE's score, EPSS, SSVC and exploit status on VulnTracker as NVD analysis and the promised PoC arrive.

References