In June 2026 CISA added CVE-2026-12569 to its Known Exploited Vulnerabilities catalog: an unauthenticated remote code execution flaw in PTC Windchill and FlexPLM, the product lifecycle management systems where many manufacturers keep their drawings, bills of materials and specifications. The catalog marks its use in ransomware campaigns as known. Over the summer, Italian data pointed the same way. ACN's Operational Summary for August 2026 put manufacturing at the top of the affected sectors, with 49 victims, mostly hit by ransomware, and Clusit's mid-year 2026 report described manufacturing as the most attacked sector in Italy. Looking back from November, the pattern is clear enough to act on. This article explains why plants are such attractive targets, what the PLM case teaches, and what to check inside the plant, from forgotten OT devices to flat networks. For how ransomware groups operate and choose victims, see our ransomware intelligence guide.
Key Takeaways
- Manufacturing led ACN's August 2026 victim count with 49 victims, mainly ransomware, and was the most attacked Italian sector in Clusit's mid-year 2026 report.
- CVE-2026-12569 in PTC Windchill and FlexPLM is an unauthenticated remote code execution flaw, in KEV since 25 June 2026 with known ransomware use.
- PLM and ERP servers hold the intellectual property that makes data-theft extortion work, and they often sit on the same network as everything else.
- Most plants cannot list every PLC, HMI and engineering workstation they run. An inventory comes before any other control.
- OT networks can be assessed safely with read-only identification and paced scanning, without writing to a controller.
Why Manufacturing Is the Top Target
The data from Italy in 2026 is consistent. ACN's Operational Summary for August, as reported by ICT Security Magazine, lists manufacturing first with 49 victims, ahead of telecommunications (43) and technology (42), and notes that manufacturing suffered mainly ransomware. The same month recorded 49 ransomware claims against Italian entities, the highest in the report's twelve-month window. Clusit's mid-year 2026 report, presented on 28 October and covered by Cybersecurity360, describes manufacturing as the sector most hit in Italy in the first half of the year.
The reasons are structural rather than mysterious:
- Downtime is expensive and visible. When the line stops, orders slip and penalties follow. That pressure is exactly what ransomware relies on.
- Networks grew flat. Office, plant, warehouse and remote maintenance often share routes that were never designed with an attacker in mind.
- Systems live for decades. A machine bought fifteen years ago may still run its original HMI on an operating system that no longer receives updates.
- Remote access is everywhere. Machine builders and maintenance providers need to connect, and each connection path is a door.
- The intellectual property is valuable. Drawings, recipes and specifications are worth stealing even when encryption fails.
The PLM and ERP Servers That Hold the IP
Product lifecycle management systems are the memory of a manufacturer: CAD models, change orders, supplier specifications, bills of materials. ERP systems hold customers, prices and production plans. Both are high-value targets for groups that now steal data before, or instead of, encrypting it.
The KEV entry for CVE-2026-12569 describes an improper input validation flaw in PTC Windchill and FlexPLM that lets "an unauthenticated, remote attacker" execute arbitrary code by sending a malicious request. It was added on 25 June 2026 with known ransomware use, a three-day due date for US federal agencies and a flag for forensic triage, meaning that agencies had to check for prior compromise as well as patch. PTC's remediation guidance is in support article CS473270.
Three questions apply to any PLM or ERP server, whatever the vendor:
- Is it reachable from the internet? Remote engineering teams and suppliers often get direct access "temporarily". Check from the outside, not from the documentation.
- Who and what can reach it from inside? If an infected office laptop can open a session to the PLM server, segmentation has failed.
- Would you notice data leaving it? A large export of CAD files at night should raise an alert somewhere.
The OT Devices Nobody Inventoried
Ask a plant for the list of its PLCs, HMIs, robot controllers, SCADA servers, engineering workstations and industrial switches, with model and firmware, and the honest answer is usually "partly". Devices arrive with machines, are configured by the supplier and are rarely added to the IT inventory. Yet an engineering workstation with the vendor's programming software installed is one of the most powerful machines in the building.
The inventory should answer, for each device: what it is (vendor, model, firmware), where it sits (which network segment, which line), who maintains it (internal team or supplier), and how it is reached (local only, VPN, vendor remote-access tool). Without that, no risk assessment, patch plan or segmentation project can start.
Segmentation and End-of-Life Systems
The reference models for industrial networks, from the Purdue model to the zones and conduits of IEC 62443, share one idea: the office network, the plant network and the control layer should be separated, with controlled, documented paths between them. In practice, three findings recur:
- Flat networks. The office VLAN can reach HMIs and PLCs directly, so ransomware that starts with an email reaches the line.
- End-of-life operating systems on HMIs, SCADA servers and engineering workstations, kept because the machine vendor only certifies that version.
- Weak Windows hygiene on the plant side: SMB signing not enforced, shared local administrator passwords, domain-joined plant machines that inherit every weakness of Active Directory.
Not every end-of-life system can be replaced quickly. It can, however, be isolated, monitored and documented as an accepted risk with a date.
How to Scan Safely on OT Networks
Plant managers are right to be wary of scanners: an aggressive scan can disturb fragile devices. That is a reason to scan carefully, not a reason not to know what is there. The principles are simple:
- Identify, do not interact. Use the identification requests each industrial protocol defines, and never write to a controller.
- Pace the traffic, especially across firewalls, and stop if the network starts blocking.
- Agree the windows with production, and start with one line or one segment.
- Verify before you report, so the plant team spends its time on real problems.
This is how RECON Internal works. A Scout probe installed on a Linux host inside your network makes outbound HTTPS connections only, so no inbound port is opened. Industrial and medical systems are queried with the identification requests each standard defines, such as Modbus Read Device Identification, BACnet Who-Is and OPC UA GetEndpoints. The probe reads; it does not write to a controller or change its state. Routed subnets behind a firewall are scanned at a paced rate, and the scan stops if the firewall starts blocking. PLCs, RTUs and controllers are identified by their own protocol, with vendor, model and firmware. Each internal scan evaluates 25 technical controls related to NIS2 Article 21, including network segmentation, SMB signing and end-of-life systems, and the Active Directory assessment shows attack paths toward privileged accounts. Each finding is re-checked and marked Proven, To verify or Closed. RECON shows that a vulnerability exists; it does not exploit it.
NIS2: Manufacturers Are in Scope
Annex II of NIS2 lists manufacturing among the "other critical sectors", covering in particular the manufacture of medical devices, computer, electronic and optical products, electrical equipment, machinery and equipment not elsewhere classified, motor vehicles and other transport equipment. Medium and large companies in those activities fall in scope; in Italy, Legislative Decree 138/2024 applies, with ACN as the authority. Food and chemicals are separate Annex II sectors. Even manufacturers outside scope are feeling it through their customers, as automotive and machinery groups ask suppliers for evidence on supply chain security. To check where your company sits, read our guide to essential and important entities.
Context: How Attackers Get In
The ACN summary also recalls CSIRT Italia bulletin BL01/260528 of 28 May 2026 on Qilin campaigns, which gained initial access by exploiting perimeter devices (Ivanti MDM and Fortinet vulnerabilities) and VPN credentials obtained by brute force or bought from access brokers, and named the lack of multi-factor authentication as the main structural weakness. Our article on the Check Point VPN zero-day used by a Qilin affiliate covers the perimeter side. Inside the plant, the question is what an attacker can reach once through that door.
Checklist: What to Look at Inside the Plant
- Build an inventory of every OT and IoT device, with vendor, model, firmware, location and maintainer.
- List every remote-access path used by machine builders and maintenance providers, and put MFA on each.
- Check from the outside whether PLM, ERP or MES servers are reachable from the internet.
- Map which office networks can reach the plant and control layers, and close the routes that are not needed.
- Find end-of-life systems, isolate them and document the accepted risk with a review date.
- Enforce SMB signing and unique local administrator passwords on plant Windows machines.
- Review Active Directory attack paths that lead from ordinary accounts to domain administrators.
- Test offline backups of PLM data and PLC programs, and rehearse restoring a line.
- Agree with production how and when scans run, and repeat them on a schedule.
If you do not yet have a reliable list of what runs on your plant network, that is the place to start. RECON Internal discovers and identifies every host, including PLCs and industrial controllers, verifies each finding and assesses Active Directory, from EUR 16.80 per asset per year. The internal scanning datasheet explains how the probe discovers, checks and verifies, in a PDF you can share with your OT team.