CVE-2026-97229: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before 19.

This week

CRITICAL 10.0REMOTEUPGRADE

CVE-2026-97229 is a critical-severity flaw (CVSS 10.0) affecting gitlab. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
EPSS top 3%: very likely to be exploited
Covered by 4 security sources
CISA SSVC: automatable with total technical impact
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	10.0 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	18.4% (top 3%)
CISA exploited list	No
Weakness	CWE-190
Published	2026-10-13
Last modified	2026-10-14

Publisher (CNA): GitLab Inc. · Vendor: gitlab

Last updated 2026-10-14 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-10-13 02:17 UTCPublished CVE record published
2026-10-14 13:55 UTCUpdated Record last modified

gitlab gitlab UPGRADE

Affected: >= 19.2.0 and < 19.2.8 · >= 19.3.0 and < 19.3.5 · >= 19.4.0 and < 19.4.2

Fixed in: 19.2.8, 19.3.5, 19.4.2

Safe to downgrade to: a release before 19.2.0

1. Check installed version

apt-cache policy gitlab || rpm -q gitlab || gitlab --version

2. UPGRADE to 19.2.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gitlab

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gitlab

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 19.2.0 (Debian / Ubuntu)

apt-cache madison gitlab sudo apt install gitlab=<VERSION_BEFORE_19.2.0> sudo apt-mark hold gitlab

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gitlab sudo dnf downgrade gitlab-<VERSION_BEFORE_19.2.0> sudo dnf versionlock add gitlab

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Debian 12 · ruby3.1 · NO FIX YET

Debian 13 · ruby3.3 · NO FIX YET

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: gandli/cve-2026-97229-lab (1 stars)
GitHub PoC: AmpedWasTaken/CVE-2026-97229-GitLab-CI-CD-Regex-Compiler-RCE (0 stars)

Advisories and coverage

Official advisories

Ruby News: Ruby 3.4.12 Released 2026-10-23
Ruby News: Ruby 4.0.9 Released 2026-10-23

Research and news

Vulners Bulletins: Exploit for Integer Overflow or Wraparound in Gitlab 2026-10-26
Rapid7 Blog: Rapid7 Analysis: GitLab CI/CD Regex Integer Overflow (CVE-2026-97229) 2026-10-16
Orca Security Blog: Critical GitLab RCE Lets Unauthenticated Attackers Execute Code on Servers (CVE-2026-97229) 2026-10-14
Rapid7 Blog: CVE-2026-97229: Critical Unauthenticated Remote Code Execution in GitLab 2026-10-13

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-97229?

gitlab: upgrade to 19.2.8, 19.3.5, 19.4.2. Exact commands for each OS are on this page.

Is CVE-2026-97229 being exploited?

CVE-2026-97229 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-97229 affect?

CVE-2026-97229 affects gitlab. Severity is critical (CVSS 10.0). 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 o

How urgent is CVE-2026-97229?

Priority 70/100. Critical severity; EPSS top 3%: very likely to be exploited; Covered by 4 security sources; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action

Software pages

GitLab vulnerabilities

Related CVEs

CVE-2026-10086 HIGH 8.7 UPGRADE GitLab has remediated an issue in GitLab EE affecting all versions from 16.4 before 18.11.6, 19.0 before 19.0.
CVE-2026-6896 HIGH 8.7 UPGRADE GitLab has remediated an issue in GitLab EE affecting all versions from 13.11 before 18.11.7, 19.0 before 19.0
CVE-2026-84284 MEDIUM 5.3 UPGRADE GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.11 before 19.2.8, 19.3 before 19
CVE-2026-82632 LOW 3.1 UPGRADE GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 before 19.2.8, 19.3 before 19.
CVE-2026-78335 MEDIUM 4.2 UPGRADE GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 before 19.2.8, 19.3 before 19.

References

← Back to latest CVEs