Annanim News
Now
Defense techReport: Australia considers buying US-made Iron Dome interceptorsCybersecurityMore than 1,000 GitLab servers still exposed to an actively exploited critical flawTools & productsWix unveils Studio Two: a site editor with an AI agent, React code and MCP supportQuantum & precision measurementSouth Korea switches on the Hangang supercomputer and will link it to a quantum computer in 2027CybersecurityCheck Point shares fall about 10% after weak third-quarter resultsDefense techElbit wins $170 million deal to build a training and simulation center for the IDF Artillery CorpsRegulation & businessElectric trucks reach 50% of heavy truck sales in ChinaCybersecurityNvidia: Brev platform breach may have exposed SSH keys to customer machinesTools & productsMusk cuts Grok Bot usage limits over "unsustainably high" costsTools & productsOpenAI is merging ChatGPT's Chat and Work tabs

Originally published:

More than 1,000 GitLab servers still exposed to an actively exploited critical flaw

GitLab fixed a maximum-severity flaw allowing unauthenticated remote code execution on October 12. CISA confirmed on Friday that it is being exploited, and Shadowserver counts more than 1,000 exposed servers that remain unpatched.

More than 1,000 GitLab servers still exposed to an actively exploited critical flaw
Image: BleepingComputer (opens the source site in a new tab)

More than 1,000 internet-exposed GitLab servers are still unpatched against CVE-2026-97229, a maximum-severity flaw exploited in remote code execution attacks, according to Shadowserver data from the weekend reported by BleepingComputer. The flaw is in the component that parses regular expressions in CI/CD pipeline configuration files and lets an unauthenticated user run code on the server.

GitLab released a fix on October 12 in Community Edition and Enterprise Edition versions 19.4.2, 19.3.5 and 19.2.8. On Friday, CISA confirmed the flaw is being exploited and added it to its Known Exploited Vulnerabilities (KEV) catalog, ordering federal agencies to secure their servers by Sunday.

What to do: anyone running self-managed GitLab should upgrade to one of the patched versions immediately. GitLab.com is already patched, and GitLab Dedicated customers do not need to take action.

Sources

Topics

Install the app

In Safari: tap the Share button, then “Add to Home Screen”.