Skip to main content
← Early warnings

BleepingComputer reports over 1,000 exposed GitLab servers unpatched against an exploited RCE flaw

BleepingComputer reports that more than 1,000 Internet-exposed GitLab servers remain unpatched against a maximum-severity flaw. The flaw is reported to be actively exploited in remote code execution attacks.

Written by a model from the sources below. Verify against them.

Sources7Reported, not confirmed
Kind
Vulnerability
Vendor
GitLab
Product
GitLab CI/CD
Status
Reported, not confirmed
First seen

What to do

  • Apply GitLab's security update to all self-managed instances now.

  • Check GitLab servers for signs of compromise or unexpected code execution.

  • Remove direct Internet exposure of GitLab instances where possible.

Timeline

  1. Made public by Mastodon
  2. First seen by cve.now2 days
  3. Record last updated

On X 10

Evidence 7

  1. Social
    Mastodon
    “CISA Warns of Active Exploitation of Maximum-Severity GitLab Regex Compiler Flaw GitLab addressed several critical vulnerabilities, including an actively exploited RCE flaw in its CI/CD regular expression compiler.”
  2. Social
    Mastodon
    “CISA says max severity GitLab flaw now exploited in the wild”
  3. Social
    Bluesky
    “GitLab security incident: attempted exploitation of CVE-2026-97229”
  4. Social
    Bluesky
    “GitLab CVE-2026-97229 (CVSS 10, no-login RCE) is on CISA KEV after an attack on Alpine's GitLab; federal deadline is today.”
  5. Press
    BleepingComputer
    “Over 1,000 Internet-exposed GitLab servers are still unpatched against a maximum-severity flaw actively exploited in remote code execution attacks.”
    +1 more: BleepingComputer on Bluesky
Show all 7 sourcesShow fewer sources
  1. Social
    Mastodon
    “Over 1,000 internet-facing GitLab servers remain unpatched against an actively exploited RCE flaw.”
  2. Social
    Mastodon
    “A # critical # vulnerability has been identified in # GitLab Community Edition (CE) and Enterprise Edition (EE) that allows an unauthenticated remote attacker to achieve Remote Code Execution (RCE) on the GitLab server.”

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about SZB-ca48ede9d9

Has GitLab confirmed it?

Mastodon, Mastodon and Bluesky report it. No statement from GitLab has reached cve.now yet.Source: Mastodon, Mastodon, Bluesky, Bluesky, BleepingComputer, Mastodon, Mastodon

What should GitLab users do?

Apply GitLab's security update to all self-managed instances now. Check GitLab servers for signs of compromise or unexpected code execution. Remove direct Internet exposure of GitLab instances where possible.