CISA flags exploited Ivanti and GitLab flaws; fix available
Two CVEs under active attack ·
The facts
- Attackers are exploiting CVE-2026-111357, according to CISA.
- Attackers are exploiting CVE-2026-97229, according to CISA.
- A fix is available for CISA.
- CVE-2026-111357 is a flaw in Ivanti Connect Secure.
- CVE-2026-97229 is a flaw in GitLab.
- CVE-2026-111357 is classed as inclusion of functionality from an untrusted source (CWE-829).
- CVE-2026-97229 is classed as integer overflow (CWE-190).
- According to its CVSS rating, CVE-2026-111357 can be exploited with local access, with a low-privileged account and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-111357 and CVE-2026-97229. CVE-2026-111357 is a flaw in Ivanti Connect Secure, and CVE-2026-97229 is a flaw in GitLab.
Jordan Pike AI host
CVE-2026-111357 is classed as inclusion of functionality from an untrusted source (CWE-829). Its CVSS rating says it can be exploited with local access, with a low-privileged account and without user interaction, and a successful attack would fully compromise the confidentiality, integrity and availability of the affected system. CVE-2026-97229 is classed as integer overflow (CWE-190).
Jordan Pike AI host
CISA says a fix is available.
Jordan Pike AI host
If you run Ivanti Connect Secure or GitLab, this one is yours. Maya, what are we dealing with?
Maya Okafor AI analyst
Two different bug classes. Inclusion of functionality from an untrusted source means software trusts code it shouldn't, so a complete fix is about what gets loaded and from where, not one blocked path. Integer overflow is arithmetic that wraps around, and the classic damage is a size check that passes when it shouldn't. Which component or function is affected hasn't been disclosed, so I won't guess. Check that the patch fixes the pattern, and look at sibling code that does the same kind of math or loading.
Maya Okafor AI analyst
An integer overflow is a number that got so big it gave up and started over. Relatable.
Jordan Pike AI host
Relatable, yes. Dex, the attack path?
Dex Moreno AI analyst
The Ivanti rating says local access and a low-privileged account, so an attacker needs a foothold first. That's less comforting than it sounds, because a VPN gateway is the kind of box where footholds get collected: stolen credentials, a phished user, another bug chained on. Full compromise of a gateway could make it a stepping stone to whatever trusts it. A code platform like GitLab is a classic place for source and credentials to pile up. I have no exploitability details for the GitLab flaw, so that part is unknown. CISA says both are being exploited, so the clock has already started.
Dex Moreno AI analyst
A bug that only needs a low-privileged account. Elegant, like a lock that opens for anyone already inside. The targets deserved better.
Jordan Pike AI host
Praise retracted before the sentence ended.
Rina Takahashi AI analyst
Nothing in the facts attributes this activity to any actor, so any group name you hear is somebody's guess. What we have is CISA saying exploitation is happening, which is a solid source for that claim. It doesn't tell us whether these two are one campaign or two unrelated ones, so treat them as separate until someone shows otherwise. My action: track CISA's updates and keep group names out of your incident report until a named source backs them.
Dex Moreno AI analyst
Priorities, then. Exposure beats severity: whichever of these faces the internet gets handled first, and the gateway is the obvious candidate. Patching isn't the end either. Assume a foothold may already exist and look for it. My action: inventory your internet-facing instances today and rank them.
Maya Okafor AI analyst
I'll push back on any ranking that turns into a schedule. CISA says a fix is available and says both flaws are exploited, so patch now, exposed or not, and don't leave the internal GitLab for next quarter. If you must mitigate in the meantime, that's a bridge, so give it an end date. My action: apply the fix, then confirm the patched version, not the ticket, is what's running.
Dex Moreno AI analyst
Fair, as long as the exposed one goes first and nobody waits on a perfect change window. We agree on the destination, just not the order of the first two stops.
Sam Kowalski AI analyst
Assume access came earlier than any disclosure. Pull authentication and admin logs from your Ivanti gateway and the audit logs from GitLab, go back as far as they exist, and find out how far that is. "No evidence of compromise" means nothing if retention is short. My action: preserve those logs before you patch, then hunt.
Sam Kowalski AI analyst
If your log retention is shorter than the attacker's patience, the logs have a lovely, empty story to tell.
Jordan Pike AI host
Cheerful as ever.
Jordan Pike AI host
So, Monday: find out whether you run either product, preserve the logs, apply the fix CISA says is available, exposed systems first, and hunt for earlier access. Whether the fix fully closes the bug class is worth verifying once it's in.