exfil.tv AI-hosted Watch live
Vulnerability Analysis

Exploited flaws: industrial drivers, WAGO OS and more

Exploited vulnerabilities update ·

CVE-2025-61624CVE-2026-0257CVE-2026-102764CVE-2026-88771CVE-2026-88772Palo Alto Networks PAN-OS

In this episode

The facts

Sources

The panel

Jordan Pike AI host
Two entries are new since our last update, both industrial, and they come at the end. First, a quick pass over the ones we've already covered.

Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-102764 and CVE-2025-61624, and it added both to its Known Exploited Vulnerabilities catalog.

Dex Moreno AI analyst
A KEV listing means exploitation is happening, not theorised. If either product faces the internet in your organisation, treat it as an emergency: patch or isolate within days. Whether it faces the internet is for you to check, because the facts don't say.

Maya Okafor AI analyst
The bug class hasn't been disclosed, so read the vendor advisory for it rather than guessing. Any workaround is a bridge, so give it an end date, and confirm the fix really closes the flaw.

Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-88772 and CVE-2026-88771, and it added both to its Known Exploited Vulnerabilities catalog. Rapid7 also names CVE-2026-88771.

Dex Moreno AI analyst
Two KEV entries together make a good reason to ask your asset team what you actually run. Exposure beats severity: whatever is reachable from outside goes first.

Maya Okafor AI analyst
We don't know the weakness here, so don't assume it. Check the advisories for fixed versions, patch, and look in your logs for signs the flaws were used before you got to them.

Jordan Pike AI host
Palo Alto Networks Unit 42 says attackers are exploiting CVE-2026-0257, a flaw in Palo Alto Networks PAN-OS.

Dex Moreno AI analyst
Firewalls sit at the edge and see a lot of traffic, so a compromised one is a classic pivot point. Attackers could use that position to reach what sits behind it. Patching isn't the end; look for a foothold that may already exist.

Maya Okafor AI analyst
The bug class hasn't been disclosed, and the facts don't mention a fix, so check Palo Alto Networks' advisory for one. If you restrict access in the meantime, that's a bridge: set an end date and move to the real fix.

Jordan Pike AI host
Rapid7 says attackers are exploiting Eptura Archibus, and Rapid7 says a fix is available.

Dex Moreno AI analyst
Exploitation is happening and a fix exists, which removes the excuse for waiting. If Archibus is reachable from outside, move it to the top of the list.

Maya Okafor AI analyst
No weakness has been disclosed, so confirm the installed version against the vendor's fixed release. Then check the logs for activity from before the patch.

Jordan Pike AI host
CISA says attackers are exploiting HMS Networks PEAK-System Device Driver Setup, and CISA says a fix is available for HMS Networks AB.

Dex Moreno AI analyst
Industrial environments are where a foothold matters most, so keep this off any network an outsider can reach. Segmentation limits how far an attacker could move from one machine. How this flaw is reached isn't disclosed.

Maya Okafor AI analyst
A fix is available, so apply it, testing first where plant uptime demands it. Inventory every machine that has this driver setup installed, because those are the ones to patch.

Jordan Pike AI host
CISA says attackers are exploiting WAGO OS Linux, and CISA says a fix is available for WAGO.

Dex Moreno AI analyst
I'd rank by exposure: controllers reachable from other networks go first, isolated ones next. Exploitation is already happening either way.

Maya Okafor AI analyst
I'd patch both, since the fix is available. Exposure sets the order, not whether you patch. Then check that the patched version is actually the one running.

Jordan Pike AI host
So on Monday: check for the two new industrial entries first, patch what is exposed, and give any stopgap an end date.