Exploited vulnerabilities / CVE-2026-97229
Confirmed exploited · remote code execution · GitLab Community Edition and Enterprise EditionCVE-2026-97229
GitLab Community Edition and Enterprise Edition remote code execution, confirmed exploited in the wild.
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.
| CISA's name for it | GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability |
|---|---|
| Vendor and product | GitLab · Community Edition and Enterprise Edition |
| Type | remote code execution · CWE-190 |
| Exploited | Confirmed by CISA listed 29 October 2026 |
| Likelihood | one of the most likely to be exploited of every vulnerability tracked |
| Deadline | 1 November 2026 · already passed |
| Used in ransomware | Not reported |
| Advisories | www.ruby-lang.org ↗ · docs.gitlab.com ↗ · www.cisa.gov ↗ · www.cisa.gov ↗ |
Three steps, in this order
Patch to the fixed version the vendor names, today if the product faces the internet.
Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list.
Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.
| CISA's required action | 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. |
|---|
Know before someone else finds it
Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.
CVE-2026-97229 in short
Is CVE-2026-97229 being exploited?
Yes. CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalogue on 29 October 2026, which it does only on evidence of exploitation in the wild.
What is the CISA deadline for CVE-2026-97229?
US federal agencies must remediate it by 1 November 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.
How likely is CVE-2026-97229 to be exploited in the next 30 days?
FIRST's Exploit Prediction Scoring System gives it 69%, the 99th percentile of every CVE it scores.
How do I fix CVE-2026-97229?
Patch to the fixed version the vendor names, today if the product faces the internet. Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list. Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.
Other GitLab vulnerabilities being exploited
| CVE | Product | Type | Listed |
|---|---|---|---|
| CVE-2026-85706 | Community Edition and Enterprise Edition | authentication bypass | 11 September 2026 |
| CVE-2021-22175 | GitLab | server-side request forgery | 18 February 2026 |
| CVE-2021-39935 | Community and Enterprise Editions | server-side request forgery | 3 February 2026 |
Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.