~/exploited / cve-2026-97229
CVE-2026-97229: GitLab Community Edition and Enterprise Edition
According to CISA this vulnerability is already used in attacks (added on 29 October 2026).
Key facts
| CVE | CVE-2026-97229 |
|---|---|
| Vendor | GitLab — Community Edition and Enterprise Edition |
| Vulnerability | GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability |
| Added | 29 October 2026 |
| Deadline (US agencies) | 1 November 2026 |
| Ransomware campaigns | unknown |
Technical data (NVD, FIRST EPSS)
| CVSS base score | 10.0 (critical) · CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HAttack over the network, complexity: low, privileges: none needed, user interaction: none |
|---|---|
| EPSS (exploitation probability) | Probability of exploitation in the next 30 days: 69.29%. Higher than 99.4% of all scored vulnerabilities (as of 18 November 2026). A high value means attacks are very likely and often already widespread. |
| Weakness type (CWE) | CWE-190 — Integer Overflow |
| Affected versions | gitlab: >= 19.2.0, < 19.2.8 gitlab: >= 19.3.0, < 19.3.5 gitlab: >= 19.4.0, < 19.4.2 ruby: >= 3.3.0, < 3.3.13 ruby: >= 3.4.0, < 3.4.12 ruby: >= 4.0.0, < 4.0.8 |
Description (NVD)
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.
Patches and vendor advisories
Description (CISA)
GitLab Community Edition and Enterprise Edition contain a integer overflow or wraparound vulnerability that could allow 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.
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
What admins should do now
- Affected? Check whether GitLab Community Edition and Enterprise Edition is in use and which version runs (package manager, admin UI,
--version). - Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
- Review logs back to 29 October 2026: unusual logins, new files, unexpected processes, outbound connections.
- If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.
The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.
Sources
- CISA KEV Catalog
- NVD CVE-2026-97229
- www.ruby-lang.org/en/news/2026/10/23/regexp-fixes-for-gitlab-cves
- docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/
- www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-base
- www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizi
- nvd.nist.gov/vuln/detail/CVE-2026-97229
New articles by e-mail
One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).