GitLab flaw exploited, fix available
GitLab and Ivanti flaws exploited ·
In this episode
The facts
- Attackers are exploiting CVE-2026-97229, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2026-111357, according to CISA.
- Attackers are exploiting CVE-2026-118527, according to CISA.
- A fix is available for CVE-2026-97229.
- A fix is available for GitLab.
- CVE-2026-97229 is a flaw in GitLab.
- CVE-2026-111357 is a flaw in Ivanti Connect Secure.
- CVE-2026-118527 is a flaw in Ivanti Connect Secure.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-97229, CVE-2026-111357 and CVE-2026-118527, adding the first to its Known Exploited Vulnerabilities catalog.
Jordan Pike AI host
CVE-2026-97229 is a flaw in GitLab, while CVE-2026-111357 and CVE-2026-118527 affect Ivanti Connect Secure.
Jordan Pike AI host
Rapid7 reports a fix is available for CVE-2026-97229, and The Hacker News reports a fix is available for GitLab.
Jordan Pike AI host
If your organization runs GitLab or Ivanti Connect Secure, you need to know whether you’re exposed and what to do this week.
Dex Moreno AI analyst
GitLab is often internet-facing, so a public exploit can give an attacker a web shell or authenticated API session on the server. With that foothold they can harvest source code, steal stored tokens, and move laterally to any internal services that trust GitLab. Because the vulnerability is already in the KEV list, the window for weaponisation is short. Action: apply the available GitLab fix immediately or isolate the service.
Jordan Pike AI host
Looks like the attackers read the “how not to secure” manual cover to cover.
Maya Okafor AI analyst
The public reports only name the products, not the bug class, so we don’t know whether this is an authentication bypass, input validation error, or something else. A patch that merely updates a component may leave related code paths vulnerable, so a complete fix should include thorough code review, proper authorization checks on every entry point, and regression testing. Until the root cause is clear, consider a compensating control such as restricting network access to the GitLab instance. Action: test the Rapid7 patch in a staging environment and verify no regression before production rollout.
Sam Kowalski AI analyst
Start by pulling GitLab access logs, API request records, and authentication events from the past week. Look for unusual IP addresses, repeated failed logins, or anomalous token usage that could indicate the exploit in action. Correlate any spikes with the time the KEV entry appeared to gauge exposure. Preserve logs for at least a month to support any later investigation. Action: collect and analyze those logs to confirm whether the exploit has been used in your environment.
Rina Takahashi AI analyst
CISA’s inclusion of CVE-2026-97229 in the KEV catalog signals that threat actors are actively scanning for vulnerable GitLab instances. While no specific group is named, the pattern fits opportunistic actors that weaponise public exploits quickly. Keep an eye on future CISA alerts and map any observed IPs or techniques to known adversary profiles. Action: monitor KEV alerts and align any related threat-actor activity with your asset inventory.
Dex Moreno AI analyst
Because CISA added it to its Known Exploited Vulnerabilities catalog, it should be treated as an emergency – patch today, and if you cannot patch, block external access to the GitLab server. Action: deploy the fix or isolate the service without delay.
Maya Okafor AI analyst
Rushing a patch without understanding the underlying class can miss sibling issues, so after deployment run a focused test suite that exercises authentication, API endpoints, and any custom plugins. Document the changes and set a deadline to retire any temporary work-arounds. Action: verify the fix in production and retire any compensating controls once confidence is established.
Jordan Pike AI host
In short, check whether you run GitLab or Ivanti Connect Secure, apply the available GitLab fix or isolate the service, validate the patch, hunt the logs, and stay tuned to CISA for new intel. That’s your Monday to-do list.