Act this weekWhat happenedCISA confirmed attackers are exploiting CVE-2026-97229, a maximum-severity GitLab flaw that can let outsiders run their own code on a server.
Who is affectedOrganizations running their own (self-managed) GitLab Community Edition or Enterprise Edition servers on versions before 19.4.2, 19.3.5 or 19.2.8.
What to do- 1Check which version of GitLab your team runs.
- 2Update to 19.4.2, 19.3.5 or 19.2.8 or newer right away.
- 3Ask your IT team to look for signs of attack, using the detections GitLab released.
- 4If your server is exposed to the internet and cannot be updated today, limit who can reach it.
Attackers are now using a maximum-severity flaw in GitLab, a popular tool software teams use to store and manage their code. The US Cybersecurity and Infrastructure Security Agency (CISA) confirmed on Thursday that the flaw, tracked as CVE-2026-97229, is being exploited. GitLab fixed it earlier this month, so the attacks target servers that have not been updated.
What changed
The flaw sits in a part of GitLab that reads automated build instructions, known as CI/CD configuration files. A researcher using the handle joaxcar found it. An attacker who is not logged in could send a specially crafted piece of text and make the server run the attacker's own code. GitLab says the cause is weak checking of that text.
After spotting exploitation attempts, GitLab released threat detections to help customers who run their own servers. CISA then added the flaw to its list of known exploited vulnerabilities.
Who it affects
The risk is for organizations that run their own (self-managed) GitLab servers, in either the Community Edition or the Enterprise Edition. Fixed versions are 19.4.2, 19.3.5 and 19.2.8. Older ones are exposed. If your company does not use GitLab, this does not touch you directly. The reports do not say how GitLab's hosted service is affected.
Shadowserver, a group that tracks internet threats, counts nearly 2,800 GitLab Community Edition servers reachable from the internet. It does not say how many are already patched, so the number of vulnerable servers is unknown.
Why it matters
A server that runs an attacker's code is effectively in the attacker's hands. For a GitLab server, that can mean a company's source code is within reach. GitLab is widely used. It says over 50% of Fortune 100 companies use it, along with more than 70 million registered users.
This is also not the first alarm this month. GitLab fixed another maximum-severity flaw in the same regular expression component (CVE-2026-110264). Almost two weeks later, it fixed a third (CVE-2026-85706), which can expose passwords and other secrets. CISA flagged that one as exploited a day later.
What to do
The alert box above lays out the steps. In short, find out which version your team runs and update it. CISA has told federal agencies to secure their servers by Sunday. That order covers only agencies, but CISA urged private companies to treat the fix as a priority too.
What happens next
Expect more scanning for unpatched servers. Earlier this month, security firm watchTowr reported attackers scanning the internet for exposed GitLab servers, and CISA has tagged six GitLab flaws as exploited since November 2021. What is still unknown is who is behind the current attacks and how many servers were hit.
The takeawayIf your company runs its own GitLab server, update it to a fixed version now, because attackers are already using this flaw.