Skip to content
Server Security Center
KEVcritical10.0

CVE-2026-97229: GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound

GitLab Community Edition and Enterprise Edition · listed in the CISA catalog of actively exploited vulnerabilities since 2026-10-29.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
74%
higher than 99.4% of all CVEs
Added to CISA KEV
2026-10-29
US federal due date 2026-11-01
Ubuntu priority
medium

CVE-2026-97229 explained

CVE-2026-97229 is an issue in GitLab Community Edition and Enterprise Edition caused by insufficient regular expression validation. Under certain conditions, a specially crafted regular expression in a CI/CD configuration could let an unauthenticated user execute arbitrary code on the GitLab server. It is listed in CISA's Known Exploited Vulnerabilities catalog, so prompt remediation matters.

Impact

An unauthenticated attacker with network access could execute arbitrary code on the GitLab server under certain conditions. No privileges or user interaction are needed, and attack complexity is low. The scope is changed, so the impact can extend beyond the vulnerable component. Confidentiality, integrity and availability impacts are all high. A successful attack could lead to full compromise of the server and the data it holds.

Who is affected

GitLab CE/EE 19.2 before 19.2.8, 19.3 before 19.3.5 and 19.4 before 19.4.2 are affected. On Debian 13 (trixie), ruby3.3 is fixed in 3.3.13-0+deb13u1. Debian 12 (bookworm) ruby3.1 has no fixed version published. Debian 14 (forky), the testing distribution, has no fixed version published for ruby3.3. Ubuntu 16.04 LTS, which is end of life, lists gitlab with no fixed version published.

Written with AI from the data on this page and checked against it automatically.

Official description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD configuration, due to insufficient regular expression validation.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • GitLab
    Affected
    • ≥ 19.2, < 19.2.8
    • ≥ 19.3, < 19.3.5
    • ≥ 19.4, < 19.4.2
    Fixed in
    • 19.2.8
    • 19.3.5
    • 19.4.2

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Upgrade GitLab CE/EE to 19.2.8, 19.3.5, 19.4.2 or later, following the vendor's instructions.
  2. On Debian 13 (trixie), update ruby3.3 to 3.3.13-0+deb13u1 or later.
  3. Restart GitLab and any services using the updated Ruby packages so they load the fixed code.
  4. Move systems on Ubuntu 16.04 LTS, which is end of life, to a supported release.
  5. Review GitLab servers for signs of compromise, since the issue is known to be exploited.

Debian 12 (bookworm) and Debian 14 (forky) have no fixed version published. Until a fix is available, limit network exposure of GitLab servers, restrict who can reach them from untrusted networks, and monitor the distribution advisory. If mitigations are unavailable, consider taking the service offline. Ubuntu 16.04 LTS is end of life; upgrade to a supported release instead of waiting.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace ruby3.3 with the source package from the table above (this CVE affects 3 source packages).

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="ruby3.3"'

2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="ruby3.3"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

No fixed version yet on 2 releases

Debian 14 (forky), Debian 12 (bookworm): no fixed version of the affected packages yet, so every installed version there is affected. Until a fix is published:

  • Follow the vendor's advisory for a mitigation or patch: docs.gitlab.com/releases/patches/patch-release-gitlab-19-…
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

Ubuntu 16.04 LTS has reached end of life and no longer gets regular security fixes – upgrade to a supported release.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-190 Integer Overflow or Wraparound

Questions about CVE-2026-97229

Does an attacker need an account to exploit this?
No. The description says an unauthenticated user could execute arbitrary code under certain conditions, and the CVSS vector lists no privileges and no user interaction required.
Is this vulnerability exploited in the wild?
CISA added it to its Known Exploited Vulnerabilities catalog on 2026-10-29, with a US federal due date of 2026-11-01. Known ransomware use is listed as unknown.
Why does Ubuntu rate this medium when the CVSS score is critical?
The facts give an Ubuntu priority of medium and a CVSS severity of critical but do not explain the difference. Treat the issue as urgent because it is known to be exploited.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.