$2.58 a Bug, No Patch in Sight: AI Finds OT Flaws Cheaply, but Fixing Them Is Still Slow

2026-11-17 · By H.A

$2.58 a Bug, No Patch in Sight: AI Finds OT Flaws Cheaply, but Fixing Them Is Still Slow

$2.58 a Bug, No Patch in Sight: AI Finds OT Flaws Cheaply, but Fixing Them Is Still Slow

Forescout's off-the-shelf AI harness found 66 new flaws in embedded TCP/IP stacks in 90 hours, but the Siemens advisory linked to the work shows the slow, expensive part is still getting fixes onto real devices.

What the research actually did

On 12 November, at 17:02 Mauritius time (13:02 UTC), Forescout's Vedere Labs published a study called "Finding Critical Infrastructure Bugs with Off-the-Shelf AI". The team returned to the type of target it had analysed by hand years earlier in its Project Memoria work: the small TCP/IP stacks built into PLCs, building controllers, medical devices, network gear and IoT products.

The team tested ten stacks. Six are open source: Contiki, Ethernut (Nut/Net), FNET, PicoTCP, lwIP and wolfIP. The other four are proprietary: Siemens' Nucleus NET and three that are still under disclosure and are not named. The researchers did not use a custom model. They used commercially available Claude models together with standard tools: Semgrep, Joern (with 32 rules they wrote), and Ghidra for the binaries.

The results:

These figures are easy to quote out of context, so the caveats matter. Building the harness, the rules and the emulation setup is not included in the cost. The "90 hours" includes human checking: Forescout's own release splits it into about 10 hours of AI analysis and 80 hours of validation. Precision also varied a lot. Across the ten stacks, between 11% and 70% of findings held up. In the authors' words, in the worst case "nine in 10" of the AI's candidate findings were wrong. Of 312 unique candidates, 99 were confirmed.

The cheap part and the expensive part

The headline says AI cut vulnerability research from months to days. Finding bugs is now cheap. Confirming them still takes expert time. Fixing them on devices that are already installed is as slow as ever, and in some cases it will never happen.

The vendor responses show this. Forescout reported 54 of the 66 new findings. The open-source maintainers of Contiki, FNET, PicoTCP, wolfIP and lwIP fixed theirs. Ethernut did not respond. Its denial-of-service bug is now public as CVE-2026-120596: a single TCP segment with an unknown option whose length byte is zero sends NutTcpInputOptions into an infinite loop and freezes every TCP service until the device is rebooted. The three unnamed proprietary stacks account for 29 findings and were still "investigating" when the report came out. One of them, S1, runs on a wireless access point that has been discontinued and whose maker no longer exists. That device has hardcoded admin credentials that cannot be changed. The researchers say plainly that no vendor will be able to provide a patch.

"Fixed" is not the same as fixed

The Siemens case shows a gap that the research summary hides. Forescout lists the five Nucleus NET findings as fixed and points to Siemens advisory SSA-333035. That advisory, published on 13 October, covers CVE-2026-89208 and CVE-2026-102073 to 102076. The affected products are building automation controllers: APOGEE PXC and TALON TC controllers, the APOGEE MBC/MEC, and a long list of Desigo PXC and PXM models.

So the stack was fixed, but many of the controllers running it will not be. For an asset owner, the question is not whether the vendor fixed the stack. It is whether the box in the plant room will ever get that fix. Usually a partner has to install the update, the site has to schedule downtime, and someone has to accept the risk of touching a controller that has worked for ten years.

Who benefits from cheap discovery

Forescout's CEO said that "containing risk, rather than patching, must be the priority". For embedded devices that is simply a description of how things already are. But cheap discovery does not help defenders and attackers equally:

None of this is surprising. It does change the timeline. The gap between a bug becoming findable and a fix reaching the device used to be protected by the cost of the research. That cost is now gone.

Practical takeaways

Sources

REEF SENTINEL