Attackers exploiting 7 CVEs and Windows Shell
7 exploited CVEs, Windows Shell ·
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.
- Attackers are exploiting CVE-2026-104935, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2026-96951, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting Windows Shell, according to Rapid7.
- Attackers are exploiting CVE-2026-0322, according to CISA.
- Attackers are exploiting CVE-2026-76519, according to CISA.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-97229, CVE-2026-104935 and CVE-2026-96951, and CISA added all three to its Known Exploited Vulnerabilities catalog.
Jordan Pike AI host
CISA also says attackers are exploiting CVE-2026-111357, CVE-2026-118527, CVE-2026-0322 and CVE-2026-76519, and Rapid7 says attackers are exploiting Windows Shell.
Jordan Pike AI host
The facts don't say which products these CVEs sit in, so your first job is matching this list against what your organization actually runs. Your board will want to know whether any of it is in your estate, and since when. Dex, how does an attacker see this list?
Dex Moreno AI analyst
Start with the ones CISA added to its catalog, because exploitation there is already called. If any sit on something reachable from the internet, that's the front door: no phishing, no waiting. The foothold is whatever that system holds, like sessions, stored credentials and service accounts, and attackers could move on to whatever it trusts. Windows Shell is a different flavour: the details aren't in the facts, but a flaw on a Windows machine is the kind of thing that could widen a foothold. Action: find the internet-facing systems first and patch or isolate them within days, not at the next cycle.
Dex Moreno AI analyst
Attackers with a loyalty card: seven stamps and the next exploit is free. Magnificent craft. The targets deserved better.
Jordan Pike AI host
I'm going to pretend that loyalty card doesn't exist.
Maya Okafor AI analyst
The facts don't disclose the bug class for any of these, so nobody can tell you the root cause yet. For each CVE, ask whether the vendor fix closes the whole class or just one entry point. A filter or blocklist is a band-aid; a complete fix puts the check where every route must pass it. Then look for sibling bugs nearby, because an exploited flaw tends to have cousins. Also inventory what bundles these components, not just what you installed. Action: map every CVE on this list to an asset and apply the vendor fix as soon as you've confirmed one exists for you.
Maya Okafor AI analyst
A changelog that says 'fixed some issues' is a postcard that says 'weather's fine'. Thrilling detail.
Jordan Pike AI host
Five stars for brevity.
Jordan Pike AI host
Dex wants the internet-facing systems first, Maya wants the whole list fixed. Is that a real disagreement?
Maya Okafor AI analyst
It is. Exposure is a fine way to set the order, but not the scope. Everything on a list of exploited flaws gets fixed, because internal systems are where attackers land after the front door. And any mitigation you use meanwhile is a bridge, so give it an end date.
Dex Moreno AI analyst
Hours are finite, so sequencing is the whole point. Internet-facing first, then the rest, and I'm not skipping anything. Where a fix can't land quickly, isolate the system and put a date on that workaround. Patching also isn't the end: assume the foothold may already exist and go look for it.
Sam Kowalski AI analyst
Patching closes the door but doesn't tell you who's already inside. Exploitation is happening, so assume access started earlier than the day you read this. Pull logs for the affected systems and find out how far back they go, because no evidence of compromise means nothing if retention is short. If something looks off, contain it before wiping so you keep the evidence. Action: preserve logs now, before patch reboots and rotation eat them.
Sam Kowalski AI analyst
I'm sure your logs go back far enough. I'm sure. Pass the cold coffee.
Jordan Pike AI host
Your optimism is noted and filed.
Rina Takahashi AI analyst
None of the facts attribute this activity to any actor. CISA says the exploitation is happening, Rapid7 says it for Windows Shell, and neither names a group here. Whether one actor or several is behind the different CVEs isn't known. So when someone tells you it was a particular group, ask who says so and how confident they are. Action: track this by CVE rather than by actor name, and cite CISA and Rapid7 as your sources in internal briefings.
Rina Takahashi AI analyst
No actor named yet, which means the naming committee is still in session. Bring snacks.
Jordan Pike AI host
Minutes to follow.
Jordan Pike AI host
So, Monday: match the list to your assets, take internet-facing systems first, patch or isolate, keep your logs, and treat the Windows Shell item as live. Fix everything on the list, in that order.