SardinhaNews

CVE-2026-97229

CriticalKEV + EUVD⏳ unpublished🧨 Metasploit🔍 NucleiSSVC ActBDU · public exploit

Published: 10/13/2026 · Modified: 11/02/2026

CVSS 3.1ⓘ10.0
EPSSⓘ69.3%
VPR (Tenable)9.5

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.

Exploitation

Requires: network access · Does not require: authentication, user interaction, special target conditions

How it is exploited

Exploitation method

  • The attacker obtains credentials for a user with push permission to a public GitLab project.
  • With those credentials, they plant a specially crafted CI configuration and repository path containing a malicious regular expression.
  • An unauthenticated request to the CI lint API compiles the regular expression, triggering an integer overflow in the Ruby regular expression compiler (Onigmo).
  • The flaw results in arbitrary command execution as the GitLab git account; each attempt allocates slightly more than 2 GiB and crashes a Puma worker after execution.

Am I affected? (applicability)

  • The environment runs GitLab CE/EE versions 19.2.0 to 19.2.7, 19.3.0 to 19.3.4, or 19.4.0 to 19.4.1.
  • The GitLab CI lint API is reachable over the network for unauthenticated requests.
  • At least one public project exists in GitLab.
  • The attacker holds credentials for a user with push permission to that public project.
  • The installation is an official GitLab CE/EE Docker image on Linux amd64 (native layout supported by the module).

Does not require: authentication, user interaction, special target conditions.

Mitigation and detection

✓ Fix available in version 19.2.8; 19.3.5; 19.4.2

  • Update to the fixed versions 19.2.8, 19.3.5, or 19.4.2.
  • Restrict network access to the GitLab CI lint API to trusted sources only.
  • Use the automated detection available in the Nuclei template to identify vulnerable instances.
  • Monitor for exploitation attempts and Puma worker crashes associated with memory allocations above 2 GiB.

Impact if exploited

Unauthenticated remote code execution as the GitLab git account — compromise of the GitLab server and the data and secrets it hosts.

Confidentiality: highIntegrity: highAvailability: high

Also affects components beyond the vulnerable one.

Community reports (unverified): exploitation 11 · PoC 14

References and technical detail

The “Requires/Does not require” line and the confidentiality, integrity and availability impact come from the official CVSS vector. Method, applicability and mitigation are an automatic summary of the NVD description, public exploitation sources (Metasploit, Nuclei, Exploit-DB) and the CVE record via CIRCL (advisories and fixed version), linked under “References and technical detail”. Community reports come from CIRCL sightings and are unverified.

Exploitation probability (EPSS) over time

10/14/202610/26/202611/01/202611/05/2026

Affected products

  • gitlab · gitlab
  • ruby-lang · ruby

Weakness type (CWE)

In the news

Timeline on SardinhaNews

References