CVE Intelligence
Critical Memory corruption exploit reference

CVE-2026-97229 — Integer Overflow or Wraparound in GitLab

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.

Published Oct 12, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitLab

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.6% (30-day exploitation probability)+7
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.56%
ahead of 45% of scored CVEs · Oct 14, 2026
Affects
Gitlab
Gitlab
CVSS base
10.0
Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Gitlab Gitlab).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Gitlab Gitlab ≥ 19.2 and < 19.2.8≥ 19.3 and < 19.3.5≥ 19.4 and < 19.4.2 Vulnerable CVE Program (cve.org) e CISA ADP
Gitlab Gitlab ≥ 19.2.0 and < 19.2.8≥ 19.3.0 and < 19.3.5≥ 19.4.0 and < 19.4.2 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
10.0 CVSS 3.1 Critical 3.9 6.0 cve@gitlab.com via NIST National Vulnerability Database
10.0 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
10.0 CVSS 3.1 Critical — — GitLab via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: cve@gitlab.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-190 · Integer Overflow or Wraparound

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.56%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Analysis and videos

CVE-2026-97229: GitLab CE/EE Integer Overflow (CWE-190) Enabling Code Execution via CI/CD Regex
GitLab has fixed CVE-2026-97229 in CE and EE for versions from 19.2 before 19.2.8, 19.3 before 19.3.5 and 19.4 before 19.4.2. According to the record, under certain conditions an unauthenticated user could execute arbitrary code on the GitLab server through a specially crafted regular expression in a CI/CD configuration. NVD and the CNA assign a CVSS 3.1 base score of 10.0 (critical), and the CVE is not listed in CISA KEV.

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · gitlab/gitlab
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · Undergoing Analysis → Analyzed
    Oct 14, 2026 · NIST National Vulnerability Database
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · gitlab/gitlab
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Undergoing Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • CVSS changed · 10.0
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 12, 2026 · GitLab

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

7 on the record

Elsewhere on this site

Gitlab
every CVE for this vendor
Memory corruption
same class
CWE-190
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-92883 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab 2d
  • CVE-2026-84284 Incorrect Authorization in GitLab 2d
  • CVE-2026-92528 Incorrect Authorization in GitLab 2d
  • CVE-2026-9268 Incorrect Authorization in GitLab 2d
  • CVE-2026-85529 Incorrect Authorization in GitLab 2d
  • CVE-2026-96893 Improper Neutralization of Input Used for LLM Prompting in GitLab 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-97229 is "Integer Overflow or Wraparound in GitLab", rated Critical. It affects Gitlab (Gitlab); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 10.0 describes technical severity. EPSS 0.56% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.