Skip to content
major vulnerability· requires attention

Unauthenticated RCE in widely used GitLab CE/EE affecting self-hosted developer infrastructure; high-impact and broadly deployed.

Applications

CVE-2026-97229

10.0
Critical
EPSS 0.56%Patch availableOct 13, 2026

Unauthenticated RCE in GitLab via crafted CI regex

common questions

Is CVE-2026-97229 being exploited?

Not confirmed. CVE-2026-97229 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.56% probability of exploitation in the next 30 days.

How severe is CVE-2026-97229?

CVE-2026-97229 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-97229?

Yes. A fix has been recorded for CVE-2026-97229. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-97229 affect?

CVE-2026-97229 affects GitLab CE/EE versions 19.2 before 19.2.8, GitLab CE/EE versions 19.3 before 19.3.5, GitLab CE/EE versions 19.4 before 19.4.2, Self-hosted GitLab instances using CI/CD. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-97229?

Upgrade to 19.4.2, 19.3.5, or 19.2.8 immediately; disable public/unknown CI runners until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
GitLab CE/EE versions 19.2 before 19.2.8GitLab CE/EE versions 19.3 before 19.3.5GitLab CE/EE versions 19.4 before 19.4.2Self-hosted GitLab instances using CI/CD
impact

Unauthenticated remote code execution on GitLab servers via malicious CI/CD regex; can lead to server takeover, data exfiltration, or supply-chain compromise.

action required

Immediate action required

affected versions
GitLab GitLab
  • affected>= 19.2 and < 19.2.8
  • affected>= 19.3 and < 19.3.5
  • affected>= 19.4 and < 19.4.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free