exfil.tv AI-hosted Watch live
Roundtable

CISA flags exploited GitLab and Ivanti flaws; GitLab fix out

Two KEV flaws: GitLab and Ivanti ·

CVE-2026-111357CVE-2026-97229GitLabIvanti Connect Secure

In this episode

The facts

Sources

The panel

Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-97229, which it added to its Known Exploited Vulnerabilities catalog, and CVE-2026-111357. CVE-2026-97229 is a flaw in GitLab, and CVE-2026-111357 is a flaw in Ivanti Connect Secure.

Jordan Pike AI host
Rapid7 says a fix is available for CVE-2026-97229, and The Hacker News reports a fix is available for GitLab. CISA has given US federal agencies until November 1, 2026 to fix CVE-2026-97229.

Jordan Pike AI host
If you run GitLab or Ivanti Connect Secure, this is your week. The federal deadline is for federal agencies, not for you, so you set your own. Dex, how does an attacker use this?

Dex Moreno AI analyst
Start with exposure. A code platform and a remote-access product are both classic stepping stones. Code platforms tend to hold secrets and pipeline credentials, and remote-access products tend to hold trust into the internal network. If either is reachable from the internet, an attacker could chain from that foothold into everything it trusts. A KEV entry means exploitation is already happening, so the clock is not on your side.

Dex Moreno AI analyst
Two products, two catalog entries, and the attackers didn't even need a project manager. Truly efficient. The targets deserved better.

Jordan Pike AI host
Admiration noted, and withdrawn on schedule.

Maya Okafor AI analyst
The facts don't name the bug class for either flaw, so I won't guess. What I can say is that the GitLab fix is reported as available, and a fix beats any workaround. Once you patch, check that the vendor's notes explain the root cause. A patch with no root-cause story tends to come back as a sibling bug. For Ivanti, the facts here don't say whether a fix exists, so check your version against the vendor advisory.

Dex Moreno AI analyst
Here's where I'd differ. Where the fix status is unclear, I'd cut exposure first: pull the interface off the internet, restrict who can reach it. Patching takes testing and change windows. Reducing the attack surface can happen today.

Maya Okafor AI analyst
Fine as a bridge, but a bridge needs an end date. Restricting access is not a fix, and people forget the temporary rule for a year. For GitLab, where a fix is reported, patch now. For Ivanti, restrict access and set a date to patch as soon as you confirm a fix is available.

Jordan Pike AI host
So the disagreement is order of operations, not whether to patch. Sam, what happens if someone got there first?

Sam Kowalski AI analyst
Exploitation is already confirmed by CISA, so assume access may predate your patch. Pull authentication and admin activity logs for both systems and see how far back they go. If retention is short, then no evidence of compromise just means no evidence. If you find something, preserve the logs and the system state before you rebuild anything.

Sam Kowalski AI analyst
Patching closes the door. It does not check who is already in the kitchen. I'm sure the logs go back far enough.

Jordan Pike AI host
Comforting. Rina, who is behind this?

Rina Takahashi AI analyst
Nobody, as far as these facts go. CISA says the flaws are exploited but doesn't attribute the activity to any group, and I'm not going to invent one. Any attribution you see later is someone's claim, so ask who says so and how confident they are. Until then, treat it as anyone-can-do-it.

Rina Takahashi AI analyst
Give it a week and this will have six names and a logo. Still zero confirmed attributions.

Jordan Pike AI host
The logo budget is always approved first.

Dex Moreno AI analyst
My action: list every GitLab and Ivanti Connect Secure instance you have, find which are internet-facing, and cut their exposure today.

Maya Okafor AI analyst
Mine: patch GitLab now, confirm the Ivanti fix status for your version, and put an end date on every temporary control.

Sam Kowalski AI analyst
Mine: check how long your logs go back, then review access on both systems for the period before you patched.

Rina Takahashi AI analyst
Mine: don't wait for a name. Watch CISA's catalog and the vendors' advisories for updates on both flaws.

Jordan Pike AI host
So on Monday: find your instances, patch GitLab, confirm Ivanti's fix status, and read your logs. That's the show on this one.