CVE-2026-97229 GitLab Community Edition and Enterprise Edition: memory-safety flaw
In plain words: The program mishandles the memory it uses to keep track of data. A specially made input can scramble that memory. Usually lets an attacker crash the program or run their own code with its permissions.
Confirmed exploited by CISA on · US federal patch deadline Nov 1, 2026
What to do
- Install GitLab's security update for Community Edition and Enterprise Edition. If no update exists, follow the vendor's workaround or stop using the product until one ships.
- Keep a list of every internet-facing server you run so nothing is forgotten.
- Patch anything in this catalog first, ahead of normal patch cycles.
- Put admin and file-transfer apps behind a VPN or single sign-on instead of the open internet.
Who is affected
Work IT. Aimed mostly at company systems — you are affected through the companies you use, not your own phone.
What's at risk: Mass data theft and ransomware: a single flaw in a file-transfer or email server has exposed thousands of organisations at once.
The details
- Official name
- GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability
- Product
- GitLab Community Edition and Enterprise Edition
- CISA description
- 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.
- Type of flaw
- Memory-safety flaw (CWE-190)
- Confirmed exploited
- Oct 29, 2026
- US federal patch deadline
- Nov 1, 2026
Ask Cleus about it
Ask about a vulnerability, an update, a weird message, or the news. Plain-word answers, free, no account.
Answering about CVE-2026-97229 ·
Questions about CVE-2026-97229
Is CVE-2026-97229 being exploited?
Yes. CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalog on Oct 29, 2026, which means there is reliable evidence of real-world attacks.
How do I fix CVE-2026-97229?
Install GitLab's security update for Community Edition and Enterprise Edition. If no update exists, follow the vendor's workaround or stop using the product until one ships. Keep a list of every internet-facing server you run so nothing is forgotten.
Am I affected by CVE-2026-97229?
Only if you use GitLab Community Edition and Enterprise Edition. Aimed mostly at company systems — you are affected through the companies you use, not your own phone.