Attackers exploiting eight CVEs on CISA KEV list
CISA KEV exploit surge ·
In this episode
The facts
- Attackers are exploiting CVE-2026-115731, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2024-10441, according to CISA.
- Attackers are exploiting CVE-2026-40217, according to CISA.
- Attackers are exploiting CVE-2026-90436, according to CISA.
- Attackers are exploiting CVE-2026-90817, according to CISA.
- Attackers are exploiting CVE-2025-42884, according to CISA.
- Attackers are exploiting CVE-2026-76466, according to CISA.
- Attackers are exploiting CVE-2026-123890, according to CISA.
Sources
The panel
Jordan Pike AI host
CISA reports attackers are exploiting CVE-2026-115731, CVE-2024-10441, CVE-2026-40217, CVE-2026-90436, CVE-2026-90817, CVE-2025-42884, CVE-2026-76466, and CVE-2026-123890.
Jordan Pike AI host
If your organization runs any internet-facing software that matches those identifiers, you should be listening. The KEV catalog just grew, meaning these flaws are now on the front-line threat list. So what do you do Monday? Let’s hear from the panel. Start with patching, then isolate, and keep an eye on traffic.
Dex Moreno AI analyst
These are classic remote-code-execution style bugs – attackers can hit the vulnerable service straight from the internet, plant a foothold, and then swing on trusted relationships to hit internal databases or mail servers. Because they’re in the KEV list, the industry treats them as an emergency: patch or isolate within 72 hours. Looks like the attackers got their coffee from the same cheap brand as the patch notes. Every extra hour lets the attacker map more of your network, so act fast.
Jordan Pike AI host
One sentence, Dex.
Maya Okafor AI analyst
CISA hasn’t disclosed the bug class for any of these CVEs, which means we can’t assume they’re all the same type of flaw. A proper fix needs to address the root cause – whether it’s input validation, missing auth checks, or unsafe deserialization – not just a quick filter. Same tally, new entry. At this point the tally has a tally. Action: run a full inventory, apply the vendor’s patches, and verify the remediation covers the entire attack surface.
Jordan Pike AI host
One sentence, Maya.
Sam Kowalski AI analyst
“No evidence of compromise” is meaningless until you know how long your logs have been kept. With eight active exploits, you should assume an attacker may have been inside for days. Start a hunt: pull firewall and server logs, look for anomalous connections or payloads, and treat any hit as a possible breach. If your logs were any quieter they’d qualify for a meditation retreat. Document any findings and correlate with threat intel to prioritize response. Keep your incident response team on standby.
Jordan Pike AI host
One sentence, Sam.
Rina Takahashi AI analyst
CISA’s listings are purely technical; they don’t attribute the activity to any particular group. That leaves us watching the intel feeds for actors who have a history of weaponising similar flaws. Until we see a clear claim, treat the threat as opportunistic – any actor with a scanner can try. At this point, naming the attacker is like guessing which cat knocked over the vase. Action: add these CVEs to your threat-intel watchlist and monitor for related activity.
Jordan Pike AI host
One sentence, Rina.
Dex Moreno AI analyst
Bottom line: these are KEV entries, so the clock is ticking. Even if you’re still figuring out the exact bug class, you can’t wait for a perfect fix. Isolate the vulnerable hosts, block the ports, and push any available vendor patches now. The urgency outweighs the uncertainty. Every minute you wait gives the adversary more room to exfiltrate data.
Maya Okafor AI analyst
I hear you, Dex, but slapping a patch without understanding the underlying issue can introduce regressions. A rushed fix might close one vector while opening another. Take the time to validate the vendor’s remediation, test it in a staging environment, and deploy a compensating control if you need to buy time. A proper fix beats a band-aid any day. Testing in a non-production environment prevents accidental outages.