Skip to main content
VulnerabilityPublished

CVE-2026-97229: Ruby · Integer Overflow or Wraparound in GitLab

Affects rubySource GCVE Database

0
Compare
Authoritative record:CVE-2026-97229· Critical 10.0

Exploited in the wild · KEV due 1 Nov 2026 · public exploit available (Metasploit) · fixed in 4.0.8 : patch ruby now.

Data as of 17 Nov 2026, 16:18 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitLab)CVSS 3.110.0
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
Patch
Available – fixed in 4.0.8, 3.4.12, 3.3.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 13 Oct 2026

  2. Weaponized: evidence found.

    1 Metasploit module

  3. Exploited in the wild: evidence found.

    Listed in CISA KEV 16 days after disclosure

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitLab Inc.

    , 19 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    exploitation active

    , 16 days after disclosure

  4. In Threat Radar

    record ingested

    , 16 days after disclosure

  5. , 16 days after disclosure

  6. KEV remediation due

    US federal deadline

    , 19 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade ruby to 4.0.8, 3.4.12 or 3.3.13.

Affected software

ProductAffectedFixed in
Bitnamirubypkg:bitnami/rubyOther threatsAffected
  • >=3.3.0 <3.3.13
  • >=3.4.0 <3.4.12
  • >=4.0.0 <4.0.8
Fixed in
  • 3.3.13
  • 3.4.12
  • 4.0.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches by upgrading GitLab to versions 19.2.8, 19.3.5, or 19.4.2 or later, which include fixes for this vulnerability. Additionally, upgrade Ruby to fixed versions 3.3.13, 3.4.12, or 4.0.8 or later. Since patchAvailable is true and fixedVersions are known, remediation is available and should be applied promptly. No other mitigation steps are indicated by the vendor advisory.

Description

A critical vulnerability in GitLab CE/EE versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 allows unauthenticated users to execute arbitrary code on the GitLab server. This occurs due to insufficient validation of specially crafted regular expressions in CI/CD configurations, leading to integer overflow or wraparound issues in Ruby versions 3.3.0 to before 3.3.13, 3.4.0 to before 3.4.12, and 4.0.0 to before 4.0.8. Public exploit code is available via Metasploit. Fixed versions have been released.

References

Community reviews

Loading reviews…