‹ All news

Follow-up · active exploitationCritical

CISA confirms active exploitation of a critical GitLab flaw that allows unauthenticated code execution

CISA has added GitLab CE/EE vulnerability CVE-2026-97229 (CVSS 10.0) to its KEV catalog; it lets an unauthenticated attacker run arbitrary code on the server. Self-managed instances not yet updated to 19.2.8, 19.3.5 or 19.4.2 are at risk.

What happened

On 29 October 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-97229 to its Known Exploited Vulnerabilities (KEV) catalog, which lists flaws confirmed to be exploited in the wild. GitLab fixed the issue in a patch release in mid-October, and NVD published it on 13 October 2026.

According to GitLab's advisory, the bug is an integer overflow in the CI/CD regular expression compiler. Due to insufficient regular expression validation, an unauthenticated attacker can use a specially crafted regular expression in a CI/CD configuration to execute arbitrary code on the GitLab server. It carries the maximum score, CVSS 10.0, and was reported to GitLab through its HackerOne bug bounty program.

Exploitation status

Inclusion in the KEV catalog means attackers are actively exploiting this flaw. CISA has set 1 November 2026 as the remediation deadline for US federal agencies; it is not yet known whether the flaw has been used in ransomware campaigns.

FIRST estimates an 18.4% probability of exploitation in the next month, higher than 97% of all known vulnerabilities. Proof-of-concept code has also been published on GitHub; it has not been verified, but its availability raises the risk and makes patching more urgent.

Who is affected

According to GitLab's advisory, the following GitLab Community Edition and Enterprise Edition releases are affected. GitLab-managed infrastructure, including GitLab.com and GitLab Dedicated, is already patched, so the exposure lies with self-managed deployments.

  • Versions 19.2 before 19.2.8
  • Versions 19.3 before 19.3.5
  • Versions 19.4 before 19.4.2

What to do

With exploitation confirmed, organisations should update without delay. GitLab has also released six threat detections to help self-managed customers spot exploitation attempts; it is worth running them retrospectively too, since the flaw has been public since mid-October. The same patch release fixes other GitLab vulnerabilities, which is a further reason to apply it.

  • Upgrade self-managed GitLab CE/EE instances to 19.2.8, 19.3.5 or 19.4.2, depending on your release line.
  • Check whether your GitLab server is reachable from the internet and restrict access as far as possible until the patch is in place.
  • Review logs for the signals GitLab describes: Onigmo native worker crash, Graphql cilint hostile regexp, ci regexp oversized non ascii path, ci regexp guard rejection, ci lint workhorse worker crash and ci lint scripted client error burst.
  • If you find signs of compromise, treat the server as breached: investigate unusual activity and rotate credentials, tokens and CI/CD secrets.

Vulnerabilities (1)

CVESeverityActive exploitationPublishedNVD status
CVE-2026-97229Critical (10)⚠ Active exploitation10/13/2026Analyzed

Written automatically from NVD, CISA KEV and vendor advisory data. Always check affected versions and patches in the vendor's official advisory before acting.