Skip to navigation

Threat reportVulnerabilityTL-2026-3356

GitLab CE/EE max-severity unauthenticated code execution flaw in CI/CD Regular Expression Compiler (CVE-2026-97229)

criticalACTIVE

GitLab disclosed CVE-2026-97229 (CVSS 10.0), an integer overflow in the CI/CD Regular Expression Compiler that could let an unauthenticated user execute arbitrary code on the GitLab server via a crafted regular expression in a CI/CD configuration. Fixed in GitLab CE/EE 19.2.8, 19.3.4 and 19.4.2; GitLab.com is already patched and self-managed instances need immediate action.

Key facts

IdentifiersTL-2026-3356, CVE-2026-97229, CVE-2026-93577, CVE-2026-89078, CVE-2026-85706, CVE-2026-92883, CVE-2026-16301, CVE-2026-14814, CVE-2026-96893, CVE-2026-81839, CVE-2026-7767
SeverityCRITICAL
CVSS10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H)
First disclosed
Exploitation statusLinked CVE exploited in the wild; Listed in CISA KEV: CVE-2026-97229 (added ), CVE-2026-85706 (added )
EPSSCVE-2026-97229: 27.6% (98.0th percentile); CVE-2026-85706: 1.1% (64.9th percentile); CVE-2026-93577: 0.5% (44.3th percentile)
Affected productsGitLab GitLab Community Edition (CE) and Enterprise Edition (EE)
Weaknesses (CWE)CWE-190
ToolsGitLab CI/CD Regular Expression Compiler, GitLab Regular Expression Parser
MITRE ATT&CK techniquesT1005 Data from Local System, T1059 Command and Scripting Interpreter, T1059.004 Command and Scripting Interpreter: Unix Shell, T1078 Valid Accounts, T1190 Exploit Public-Facing Application, T1195.002 Supply Chain Compromise: Compromise Software Supply Chain, T1213.003 Data from Information Repositories: Code Repositories, T1528 Steal Application Access Token, T1539 Steal Web Session Cookie, T1552.001 Unsecured Credentials: Credentials In Files, T1565.001 Data Manipulation, T1585 Establish Accounts
MotivationUNKNOWN
Target sectorstechnology, software-development, government administration, finance, telecoms
Target regionsGlobal
Detection rules9 (1 shown free)
Sources10 cited sources

Detection coverage

As of 2026-10-13, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-3356 across Splunk SPL, Microsoft KQL and Sigma, covering 28 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: GitLab CI Lint Abuse - CVE-2026-97229 Regex Compiler Exploitation (SPL)

Flags abuse of the GitLab CI lint API, which evaluates CI/CD configuration through the Regular Expression Compiler vulnerable to CVE-2026-97229 (unauthenticated, CVSS 10.0) and CVE-2026-93577 (authenticated). Looks for bursts, anonymous callers, slow or crashing responses and oversized bodies. The endpoint is an assessed hunting lead, not a sourced IOC; no public PoC exists.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1190, T1078, T1195.002
  • Data sources: gitlab:production_json (Splunk index=gitlab), CommonSecurityLog (reverse proxy / WAF CEF), webserver access logs (Sigma category webserver)
  • Severity: high
  • Confidence: medium

Splunk SPL

index=gitlab sourcetype="gitlab:production_json" method=POST (path="/api/v4/ci/lint" OR path="/api/v4/projects/*/ci/lint") earliest=-24h
```CVE-2026-97229 / CVE-2026-93577: crafted regex in CI config reaches the CI/CD Regular Expression Compiler via the lint endpoint; flag bursts, anonymous callers, slow or crashing (5xx) requests```
| eval anon=if(isnull(username) OR username="" OR username="-", 1, 0), server_err=if(tonumber(status)>=500, 1, 0), slow=if(tonumber(duration_s)>5, 1, 0)
| bin _time span=10m
| stats count AS requests, sum(anon) AS anonymous_requests, sum(server_err) AS server_errors, sum(slow) AS slow_requests, values(ua) AS user_agents, values(path) AS paths BY _time, remote_ip
| where server_errors>=1 OR slow_requests>=1 OR anonymous_requests>=5 OR requests>=20
| sort - server_errors, - requests

Microsoft KQL

CommonSecurityLog
| where TimeGenerated > ago(24h)
| where RequestMethod =~ "POST"
| where RequestURL matches regex @"/api/v4/(ci/lint|projects/[^/]+/ci/lint)"
| summarize Requests = count(), MaxRequestBytes = max(ReceivedBytes), UserAgents = make_set(RequestClientApplication, 5), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationHostName, bin(TimeGenerated, 10m)
| where Requests >= 20 or MaxRequestBytes >= 65536
| project TimeGenerated, SourceIP, DestinationHostName, Requests, MaxRequestBytes, UserAgents, FirstSeen, LastSeen

Sigma

title: GitLab CI Lint Endpoint Server Error - CVE-2026-97229 Regex Compiler Exploitation
id: 7c1e4f52-3a9d-4b6e-8f21-5d0a9c3e7b14
status: experimental
description: Detects POST requests to the GitLab CI lint API (/api/v4/ci/lint) that end in a 5xx response, a possible crash or failure of the CI/CD Regular Expression Compiler when handling a crafted regular expression (CVE-2026-97229, related CVE-2026-93577).
references:
    - https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/
    - https://www.bleepingcomputer.com/news/security/gitlab-warns-of-max-severity-rce-flaw-in-regex-compiler-engine/
    - https://intel.threadlinqs.com
author: Threadlinqs Team
date: 2026-10-12
tags:
    - attack.initial-access
    - attack.t1190
    - attack.t1078
    - attack.t1195.002
    - cve.2026.97229
    - cve.2026.93577
logsource:
    category: webserver
    product: gitlab
detection:
    selection_lint:
        cs-method: 'POST'
        cs-uri-stem|re: '^/api/v4/(ci/lint|projects/[^/]+/ci/lint)$'
    selection_failure:
        sc-status:
            - 500
            - 502
            - 503
            - 504
    condition: selection_lint and selection_failure
falsepositives:
    - CI linting from IDE plugins or pipeline editors during a GitLab restart or Puma worker recycle
    - Vulnerability scanners or load tests that exercise the CI lint API
level: high

Known false positives:

  • CI editors, IDE plugins and pipeline-validation tooling that call /api/v4/ci/lint at high rate
  • Vulnerability scanners and load tests against self-managed GitLab

Tuning notes: Baseline lint request volume per remote_ip and allowlist known CI tooling and scanner ranges. Raise the burst threshold (20 per 10 minutes) for busy instances. Ingest production_json.log (gitlab:production_json) and map CEF body size to ReceivedBytes on the proxy. Correlate hits with commits touching .gitlab-ci.yml and with GitLab version below 19.2.8, 19.3.4 or 19.4.2.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • GitLab CI Lint Abuse - CVE-2026-97229 Regex Compiler Exploitation (KQL) · unlock with TL Creds
  • GitLab App Process Spawns Shell or Downloader - CVE-2026-97229 Post-Exploitation (KQL) · unlock with TL Creds
  • GitLab Host Secret and Repository Collection - CVE-2026-97229 Follow-On (KQL) · unlock with TL Creds
  • GitLab CI Lint Abuse - CVE-2026-97229 Regex Compiler Exploitation (Sigma) · unlock with TL Creds
  • GitLab App Process Spawns Shell or Downloader - CVE-2026-97229 Post-Exploitation (Sigma) · unlock with TL Creds
  • GitLab Host Secret and Repository Collection - CVE-2026-97229 Follow-On (Sigma) · unlock with TL Creds
  • GitLab App Process Spawns Shell or Downloader - CVE-2026-97229 Post-Exploitation (SPL) · unlock with TL Creds
  • GitLab Host Secret and Repository Collection - CVE-2026-97229 Follow-On (SPL) · unlock with TL Creds

Indicators of compromise

As of 2026-10-13, Threadlinqs Intelligence tracks 28 indicators of compromise for TL-2026-3356.

28 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

CVE-2026-97229 is an integer overflow (CWE-190) in the regular expression compiler that GitLab uses to parse, compile and evaluate regular expressions found in projects' CI/CD pipeline configuration files. GitLab's advisory states that, under certain conditions and due to insufficient regular expression validation, an unauthenticated user could execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD configuration. GitLab scores the issue CVSS 3.1 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Affected versions are GitLab CE/EE 19.2 before 19.2.8, 19.3 before 19.3.4 and 19.4 before 19.4.2. The flaw was reported by the researcher 'joaxcar' through GitLab's HackerOne bug bounty program. The GitLab advisory does not list a CWE; CWE-190 is derived from the advisory title (integer overflow).

The fix shipped in patch release 19.4.2 (together with 19.3.4 and 19.2.8), which addresses 25 security vulnerabilities in total (CVE-2026-97229 plus 24 others ranging from low to high severity, including XSS, authorization and SSRF issues). GitLab.com and GitLab Dedicated are already patched. Single-node self-managed instances will see downtime during the upgrade; multi-node instances can apply the patch with zero-downtime procedures. At the time of the BleepingComputer report (2026-10-12) there was no reported active exploitation, no public proof-of-concept and no published indicators of compromise; the NVD API returned no record for the CVE at research time.

This appears closely related to an earlier fix: CVE-2026-93577, published with patch release 19.4.1/19.3.3/19.2.7 on 2026-09-23, is also an integer overflow in the same Regular Expression Compiler, reported by the same researcher, with CVSS 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) requiring an authenticated user. The same release also fixed CVE-2026-89078, a double free in the Regular Expression Parser (CVSS 9.9, authenticated, reported by joaxcar); that release fixed 11 vulnerabilities in total. Sources do not state that CVE-2026-97229 is a bypass or incomplete fix of CVE-2026-93577; defenders should treat the regex-compiler component as a repeated bug class and patch to the latest releases. Exploit mechanics beyond the advisory text (memory-corruption primitive, payload construction, reliability) are not publicly documented.

GitLab self-managed servers have a recent history of rapid weaponization: BleepingComputer notes CVE-2026-85706, a max-severity path traversal / authentication bypass in the repository commits API (fixed 2026-09-12 in 19.1.8, 19.2.6 and 19.3.2), was added to CISA's KEV catalog, with internet-wide probing and public PoC code reported shortly after disclosure per third-party reporting (SOC Prime, Rapid7, SOCRadar). That is a separate flaw and not evidence of exploitation of CVE-2026-97229, but it justifies urgent patching.

Defensive relevance: a self-managed GitLab server holds source code, CI/CD variables, runner registration tokens, deploy keys and service credentials, so code execution on the application host is a high-value supply-chain pivot. Post-exploitation techniques mapped below are assessed impacts of server-side code execution on a CI/CD platform and are not reported in-the-wild behavior.

MITRE ATT&CK techniques by tactic:

Collection

T1005 Data from Local System; T1213.003 Data from Information Repositories: Code Repositories

Execution

T1059 Command and Scripting Interpreter; T1059.004 Command and Scripting Interpreter: Unix Shell

Initial Access

T1078 Valid Accounts; T1190 Exploit Public-Facing Application; T1195.002 Supply Chain Compromise: Compromise Software Supply Chain

Credential Access

T1528 Steal Application Access Token; T1539 Steal Web Session Cookie; T1552.001 Unsecured Credentials: Credentials In Files

Impact

T1565.001 Data Manipulation

Resource Development

T1585 Establish Accounts

Remediation

Patches

  • GitLab CE/EE 19.2.8
  • GitLab CE/EE 19.3.4
  • GitLab CE/EE 19.4.2

Immediate actions

  • Upgrade self-managed GitLab CE/EE to 19.2.8, 19.3.4 or 19.4.2 (or later) immediately
  • Review GitLab application, Rails and Sidekiq logs and runner activity for anomalous pipeline creation, unusual .gitlab-ci.yml regular expressions and unexpected child processes of the GitLab application
  • Restrict network exposure of self-managed instances (VPN / IP allowlisting) until patched

Workarounds

  • No vendor workaround stated in sources; GitLab.com and GitLab Dedicated are already patched
  • For the related authenticated CVE-2026-93577, third-party sources suggest limiting who may modify CI/CD configuration (Developer-level access, protected branches); this is not a substitute for patching

Longer-term hardening

  • Subscribe to GitLab security release notifications and patch critical releases within days
  • Rotate CI/CD variables, runner tokens, deploy keys and access tokens if compromise is suspected
  • Monitor GitLab host with EDR and alert on shell or interpreter children of GitLab application processes

Affected and fixed versions

  • GitLab — GitLab Community Edition (CE) and Enterprise Edition (EE)
    Vulnerable versions: 19.2 before 19.2.8; 19.3 before 19.3.4; 19.4 before 19.4.2
    Fixed in: 19.2.8; 19.3.4; 19.4.2

Timeline

Last updated · 4 updates · revalidated 4× · latest source

  • Separate GitLab max-severity flaw CVE-2026-85706 (path traversal / auth bypass) added to CISA KEV per third-party reporting, with internet-wide probing observed; context for the elevated risk to self-managed GitLab
  • GitLab patches CVE-2026-85706 in 19.1.8, 19.2.6 and 19.3.2
  • GitLab releases patch 19.4.1/19.3.3/19.2.7 (11 fixes) including the related authenticated regex-compiler integer overflow CVE-2026-93577 (CVSS 9.9) and double free CVE-2026-89078 (CVSS 9.9), both reported by joaxcar via HackerOne
  • Third-party databases (Wiz, OpenCVE) index CVE-2026-93577 for GitLab 19.2-19.4
  • Release breakdown per newer report: 25 fixes (1 critical, 6 high, 12 medium, 5 low, 1 EE-only medium); database migrations must complete before startup on 19.3.5.
  • Same patch release also fixes CVE-2026-7767 (CVSS 5.8 open redirect in the Kubernetes proxy that could leak authentication tokens), also reported by joaxcar.
  • BleepingComputer reports the max-severity flaw; no active exploitation, public PoC or IOCs reported
  • GitLab states GitLab.com and Dedicated are already patched; self-managed instances must upgrade
  • GitLab patch release 19.4.2 (with 19.3.4 and 19.2.8) fixes CVE-2026-97229 and 24 other security issues
  • Rapid7 releases authenticated vulnerability checks for Exposure Command, Vulnerability Management and Nexpose in the 2026-10-13 content release.
  • Rapid7 publishes its Emerging Threat Response analysis describing the US-ASCII/UTF-8 encoding mismatch and Onigmo integer overflow; further root-cause analysis promised.
  • Rapid7 reports independent reproduction of code execution against the GitLab 19.4.1 CE official image with ASLR enabled; 19.4.2 resists the same input.
  • GitLab's patch page and NVD list 19.3.5 as the fixed 19.3 release; 19.3.4 is cited by some secondary sources but had an unrelated merge request page bug fixed in 19.3.5. Defenders should target 19.3.5.
  • GBHackers reports the flaw; no active exploitation or public proof of concept reported at time of publication.
  • NVD publishes CVE-2026-97229 (CWE-190, CVSS 3.1 10.0) referencing the GitLab patch notes and HackerOne reports 4055749 and 4058589.
  • Expected public release of full vulnerability details, 90 days after the 2026-10-12 patch release per GitLab policy; public PoC likelihood rises after this date.

Update history

Sources cited

Other reports on CVE-2026-97229

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 10 sources; published ; last updated .

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats