Search/wago
Known CVEs
0
Highest CVSS
In KEV
0
Vendor
750-831/000-002 firmware
Connections
152 relationships
Researchers Use Claude to Port Pre-Auth RCE Exploit From One PLC Model to Another
Forescout Research - Vedere Labs said it used Anthropic's Claude to port a working pre-authentication remote code execution (RCE) exploit from one WAGO programmable logic controller (PLC) to another, executing attacker-supplied ARM shellcode on live hardware. The exploit targets CVE-2021-31886, a stack-based buffer overflow in the Nucleus FTP server's handling of the USER command, which carries a Siemens-assigned CVSS score of 9.8 and is accessible before authentication over TCP port 21. CERT@VDE says no updates are available for the affected WAGO controllers, and advises owners to disable or block FTP on port 21, enforce segmentation controls, and monitor network traffic for anomalies. The port required sustained researcher steering, and the final RCE development stage consumed $535.74 in application programming interface (API) usage over an 8-hour-32-minute session. A later session that attempted to extend the exploit into a command-and-control (C2) implant wrote to a flash-mapped memory region, permanently bricking the PLC. "One could argue that the same researcher could have achieved the initial RCE port without AI in less time and at lower cost while also keeping the PLC alive," Forescout said. Vedere Labs had previously developed a working RCE exploit for the WAGO 750-852, and ported that exploit to a WAGO 750-831 running firmware V01.04.16. The researchers supplied the existing 750-852 exploit, a firmware binary for the 750-831, and a physical 750-831 as the live target. Each stage ran as interactive sessions between a researcher and Claude Code, which had access to a terminal, the reverse-engineering tool Ghidra, and the target PLC. The work began on Claude Sonnet 4.6 and moved to Claude Opus 4.6 after the initial RCE attempts stalled. Normal FTP processing on the 750-831 zeroed 256 bytes at the attacker-controlled buffer, so the injected shellcode was overwritten before it could run. Claude adapted the USER and QUIT sequence used against the 750-852 into a USER and CWD sequence. Omitting the CRLF terminator then "prevented the relevant processing path from completing in the usual way," Forescout said. The buffer survived long enough for the payload to execute. Once code execution was established, the model moved from working no-operation (NOP) shellcode to two functional payloads in 12 minutes, Forescout said. One sent ICMP echo requests to an attacker-controlled system, and the other sent a UDP packet containing the string PWNED. The exploit runs in the Ethernet receive callback context, and the demonstrated capability stops at the point of sending network packets. Vedere Labs has previously shown that RCE on a controller can be chained to enable deep lateral movement in operational technology (OT) networks, exploiting multiple vulnerabilities in Schneider Electric Modicon PLCs. Forescout said the model also flagged a potential bug in the FTP command extraction loop, distinct from CVE-2021-31886, during the first session. Manual review "suggested that this may be a separate, previously unidentified, vulnerability," Forescout said. The team set it aside for separate investigation, and the issue carries no CVE identifier. A GitHub repository search for CVE-2021-31886, run by The Hacker News on September 1, returned no results, and the flaw is absent from Exploit-DB and Packet Storm. That search indexes repository names and descriptions rather than file contents. "The more immediate risk is not an agent independently deciding to attack a controller, but an authorized agent taking the wrong action on a physical system where failure has real operational consequences," Forescout said. The CERT@VDE advisory for WAGO lists the following devices as vulnerable to all the flaws in that advisory, including CVE-2021-31886 - 750-829 (FW16 and earlier) 750-831/000-00x (FW14 and earlier) 750-852 (FW16 and earlier) 750-880/0xx-xxx (FW16 and earlier) 750-881 (FW16 and earlier) 750-882 (FW16 and earlier) 750-885/0xx-xxx (FW16 and earlier) 750-889 (FW16 and earlier) 750-331 (FW16 and earlier) 750-352/xxx-xxx (FW16 and earlier) "The listed fieldbus coupler and PLCs above are based on Nucleus V1 RTOS. At the moment, there are no updates for this version available," the advisory said. Two of those models, the 750-882 and the 750-885/0xx-xxx, are absent from both the advisory's mitigation section and its remediation table, leaving their fix status unstated. Siemens, which maintains Nucleus, states in its Nucleus advisory that no remediation is planned for Nucleus NET across all versions, and that Nucleus ReadyStart V3 releases from V2013.08.1 onward already fix CVE-2021-31886. The flaw was one of 13 disclosed in November 2021 as NUCLEUS:13 by Forescout and Medigate. In its earlier research on chaining PLC exploits, Forescout concluded that the issues discussed "should likely not be near the top of your priority list," and said AI advances should make organizations reconsider that risk calculus. The research follows a joint advisory issued August 19 by the NSA, CISA, FBI, Department of Energy, and Environmental Protection Agency, which warned of an active threat to internet-exposed Siemens S7 Series PLCs from AI-generated exploitation scripts. The agencies assess that the activity is likely intended for persistent reconnaissance and capability development and have stopped short of attribution. Separately, the FBI and the EPA reported attacks on water utilities in at least seven states since July 27, some of which degraded operations. Those actors changed IP addresses and passwords on internet-facing Rockwell Automation MicroLogix controllers, in attacks that needed no exploit. "Using AI to generate exploitation scripts represents an evolution in threat actor capabilities, dramatically reducing the technical expertise and time required to develop working ICS exploitation scripts and malicious tools," the authoring agencies said in the joint advisory.
thehackernews.comSep 2, 2026extracted
Experiment: Porting a PLC Exploit With AI Takes Hours and Hundreds of Dollars
Researchers at Forescout’s Vedere Labs used Anthropic’s Claude to port a working remote code execution (RCE) exploit from one WAGO programmable logic controller (PLC) to another. They succeeded but only after extensive researcher oversight, several hours of dedicated work, and hundreds of dollars in API costs. The starting point was a previously developed exploit for the WAGO 750-852 PLC, based on CVE-2021-31886, a pre-authentication buffer overflow in the Nucleus FTP server that allows an unauthenticated attacker to execute arbitrary ARM shellcode on the targeted PLC. For their experiment, Forescout researchers set out to adapt that exploit to a related but distinct model, the WAGO 750-831, and to see whether the AI could then push the result further into a full command-and-control implant. The experiment was conducted in the wake of the recent attacks targeting PLCs in the water sector. The researchers used Claude Code, giving it access to a terminal, reference files, the reverse-engineering tool Ghidra, and the physical target device. The AI confirmed the vulnerability through a mix of live probing and static firmware analysis before generating a payload that crashed the PLC. The crash confirmed the flaw was present, but this was the easy part of the exercise. Turning it into controlled code execution took far longer, and early attempts sent the AI chasing incorrect leads, requiring researchers to redirect its analysis and provide additional technical context. Progress stalled until the team switched from Claude Sonnet 4.6 to Claude Opus 4.6 and instructed the model to ask for help whenever it was uncertain about a firmware detail. The breakthrough came when the AI figured out why the injected code kept getting erased before it could run, then adjusted its approach to keep the payload intact. Once that obstacle was cleared, Claude produced two separate working payloads within 12 minutes. The researchers note that this pattern — a difficult, time-consuming path to initial execution followed by rapid iteration afterward — is what makes the cost of scaling this kind of work worth watching. A follow-up attempt to build on the RCE went less smoothly. In a new session aimed at developing a command-and-control implant, Claude tested increasingly complex payloads, and one of those payloads wrote to a region mapped to the PLC’s flash memory, permanently bricking the device. As for the costs associated with the experiment, Forescout noted that the final stage of RCE development alone consumed over $500 in API usage across a session lasting more than eight hours. “One could argue that the [researcher guiding the AI] could have achieved the initial RCE port without AI in less time and at lower cost while also keeping the PLC alive,” Forescout noted, adding, “That is true right now, but the more important question is what happens as the amount of expert intervention required continues to fall. A human researcher can parallelize this work, but AI has the potential to reduce the marginal cost of doing so across many related targets at once.” Related: Hackers Using AI to Target Siemens PLCs in Critical US Sectors Related: CISA Urges Water Sector to Protect OT After Coordinated Attacks on PLCs Related: CISA: Over 100 Internet-Exposed Water Systems Targeted in July Cyberattacks
securityweek.comSep 1, 2026extracted
Russian-Linked Hackers Accessed Polish Power Plant OT Network Through Private APN, Says CERT.PL
The Polish CERT (CERT.PL) has published details of another attack on its energy infrastructure which took place during a suspected Russian cyber campaign in December 2025. The post mortem on the attack took three months to complete and was therefore not included in the initial report published in January 2026. That report detailed a late 2025 cyber-attack on Poland's energy infrastructure involving wiper malware and attributed to Sandworm, a Russian state-backed APT group. The latest report details a series of novel techniques which enabled attackers to force the shutdown of a steam turbine and water treatment system at a large combined heat and power (CHP) plant in the country which serves 50,000 residents. It is the first known documented attack in which threat actors have accessed an OT network through a private Access Point Name (APN), the CERT claimed. The attack began after adversaries compromised a FortiGate VPN + firewall at a wind farm in the country. They then used a Teltonika cellular router on the same network to target a private APN network managed by a distribution system operator (DSO) via an SSH tunnel. They scanned the APN repeatedly and were able to find a WAGO PFC200 programmable logic controller (PLC) at the CHP plant. Its web interface was accessible via the APN and protected only by default admin credentials. After compromising that controller, the actors used SSH to access the plant’s OT network, before scanning for and finding three Siemens PLCs. “According to statements provided by CHP plant personnel, the PLCs were switched to STOP mode and protected with a password that prevented changes to their operating state and modification of the control logic,” the report explained. “As a result, the steam turbine and the water treatment system used to produce process water were shut down, leading to an interruption of the cogeneration process.” As part of efforts to stall the recovery process, the attackers sabotaged several Moxa network devices, destroyed logs, damaged the WAGO controller, reset the Teltonika router, and restored the FortiGate device to factory settings. Recommendations from CERT.PL The CERT urged any organizations using solutions based on private APNs to do the following: Conduct an audit of their private APN configuration, and enable client isolation between end devices connected to the APN Treat the private APN as an untrusted network and segment from the OT environment Strictly limit communications between the OT network and the device acting as the gateway to the private APN Monitor traffic between the OT network and the private APN, and flag any abnormal activity Implement centralized logging and monitoring of events generated by devices serving as gateways to the private APN Minimize the number of open ports accessible via interfaces reachable from the private APN Change default credentials for all services available on devices connected to the private APN, especially administrative services Include private APNs and the devices providing access to them within the scope of penetration tests, red team exercises, and security architecture reviews Fortunately, on this occasion, the outage didn’t last long and no customers suffered power loss. However, it came during a major Russian campaign linked to the infamous Sandworm group which targeted 30 Polish renewable energy facilities and another large CHP plant. These attacks took place on December 29 and 30 2025.
infosecurity-magazine.comAug 12, 2026extracted
Hackers Breach Polish Power Plant Controls via Private Cellular Network and Shut Turbine
Attackers shut down a steam turbine and the process-water treatment system at a Polish combined heat and power plant by coming in over the private cellular network the local grid operator uses to reach remote equipment. The plant supplies heat to roughly 50,000 residents. Recovery began at about 7:30 a.m. while the intruders were still active inside the network, and customers lost neither heat nor electricity. CERT Polska disclosed the December 2025 incident on August 8 after an investigation lasting more than three months. Poland's prime minister had said in January that two CHP plants were hit. This is the second. The route ran through a private APN, or access point name: a dedicated cellular data network managed by the distribution system operator. A configuration that allowed arbitrary devices on that APN to communicate with one another let the attacker pivot from a compromised wind-farm network to a controller at the CHP plant. CERT says reaching an industrial control network through a private APN was, to the best of its knowledge, "the first instance of this attack vector being observed in a real-world cyberattack." The wind farm and the plant are separate facilities, and neither of them runs the network that linked them. The report does not establish a CVE as the cause of the intrusion, and investigators could not determine whether a vulnerability in the Teltonika router had been exploited, so there is no single software patch to apply. The WAGO controller reachable through the APN still had default admin credentials, while the private APN allowed client-to-client traffic. CERT's first recommendation is to audit the private APN configuration and switch on client isolation. It also advises treating the APN as untrusted from the operational technology (OT) side, segmenting and restricting traffic, removing unnecessary management services from APN-reachable interfaces, and changing default credentials. CERT says its surveys found that Polish organizations running private APNs commonly let any device on the network reach any other. It believes similar configurations are widely deployed in other countries. The router's SSH service, the controller's web interface and the permissive APN were all working as configured. The attack path began at a wind farm, where a FortiGate device served as both firewall and VPN concentrator. Its VPN was exposed to the internet and allowed accounts without multi-factor authentication. The attacker had administrative privileges on the device and likely used them to obtain VPN credentials that could reach all network segments. The distribution operator required communications to the substation's remote terminal unit to run over the serial DNP3.0 protocol, and that requirement was met. But no equivalent requirements covered the cellular router's management interface, which sat on a second interface, an Ethernet port connected to a VLAN behind the compromised firewall. The wind farm met the DNP3.0 requirement it had been given and still supplied the route in. That requirement governed how data travelled, not how the device carrying it was administered. The router was a Teltonika RUTX50 whose default password had been changed during deployment. Investigators recovered repeated successful SSH logins but could not establish how the attacker obtained that password. As of August 11, The Hacker News reviewed the published vulnerabilities in the router's own firmware and found none that would hand an unauthenticated attacker its password. The two RUT-series flaws in CISA's 2023 Teltonika advisory, CVE-2023-32349 and CVE-2023-32350, both require existing privileges on the device, and the RUTX50's modem flaws cause only denial of service. An unpublished flaw is not ruled out. Mobile-operator logs led CERT to assess that the attacker most likely used SSH tunneling through the router to reach the private APN. Starting December 18, the attacker scanned the APN and found a WAGO PFC200 controller exposing its web administration interface with default admin credentials. Subsequent SSH activity suggests the service was likely enabled through that interface, and timestamp correlation led CERT to assess that the attacker most likely tunneled through the WAGO into the plant's OT network. On December 25, the attacker successfully connected to three Siemens PLCs over the S7 protocol, activity CERT considers most likely to have been reconnaissance for the later destructive actions. On December 29, attacker activity inside the CHP network ran from about 5:30 a.m. until about 10:10 a.m., with plant recovery beginning at about 7:30 a.m. According to plant personnel, Siemens S7-300, S7-1200, and S7-1500 controllers were switched to STOP mode and password-protected, shutting down the turbine and the process-water treatment system and interrupting cogeneration. Seven Moxa serial device servers and three switches were also factory-reset, given changed passwords and assigned unreachable IP addresses such as 127.0.0.1. CERT says the timing indicates with a high degree of confidence that those actions were automated. None of it required malware, and the report describes none. Every destructive step used a supported device function, invoked over the protocols the plant runs on. The attacker then damaged the way in. The WAGO controller's partition table was corrupted, leaving it unable to boot and yielding no useful logs. About 30 minutes after the last observed activity at the CHP plant, the attacker factory-reset the Teltonika router, changed its administrator password and assigned it the unreachable address 127.0.0.1, then factory-reset the FortiGate, causing its logs to be lost. CERT says RutOS versions earlier than 7.07 retained their event database after a factory reset, which is why the SSH login records survived. The plant did not initially read it as an attack. Maintenance was underway, so the operator logged the interruption as probable contractor error and reported it for information only; CERT opened an incident because it already knew of similar events. Reconnaissance inside the plant's network had run from December 18 to 25, including a port scan that started at the SCADA system's address. No actor is named for this incident. The wider December campaign drew four separate assessments in January, from Poland's government, CERT Polska, ESET, and Dragos. Each is scoped differently, to the campaign's preparation, its infrastructure, the wiper malware used against its other targets, and its broader shape. None of them addresses this intrusion. Private APNs still appear in federal guidance as an isolation option. A July 30 FBI and EPA advisory on attacks against internet-facing water-sector PLCs lists a private APN among the isolated architectures operators should consider for reaching OT equipment over cellular links.
thehackernews.comAug 11, 2026extracted
Previously unseen entry vector used to breach Polish energy plant
Previously unseen entry vector used to breach Polish energy plant The December 29 cyberattack on a Polish combined heat and power (CHP) plant was the first observed case of attackers gaining access to an OT network through a private APN, according to CERT Polska. The private APN is a dedicated mobile network that a Distribution System Operator (DSO), the company running the local electricity grid, sets up with a mobile carrier. Illustrative use of a private APN in distributed energy resources (Source: CERT Polska) The incident happened on the same day as coordinated attacks against Poland’s energy sector that affected 30 renewable energy facilities and another CHP plant. CERT Polska said analysis of the smaller CHP plant took more than three months, so the incident was left out of its initial report. The targeted CHP plant supplies heat to around 50,000 residents. The attack shut down a steam turbine and the water treatment system used to produce process water, interrupting the cogeneration process. Operators restored the installation before the incident disrupted heat or electricity supplies to customers. Maintenance work happened to be underway at the plant that day, so staff first assumed the contractor’s engineers had made a mistake and reported the incident only for informational purposes. CERT Polska was aware of similar events elsewhere and investigated the possibility of a cyberattack anyway. “Further analysis confirmed this hypothesis,” the report states. Marcin Dudek, head of CERT Polska, revealed details of the attack at DEF CON 34 in Las Vegas. “What first looked like human error turned into a three-month hunt through false leads, forgotten remote access devices, wiped industrial hardware, cellular connectivity, and infrastructure that was assumed to be isolated,” Dudek said. “Based on further detailed analysis of the collected logs, investigators were able to identify the device from which the attacker had conducted their activities: a WAGO PFC200 PLC equipped with an integrated cellular modem,” researchers wrote. “Unfortunately, the device had been damaged, and no data could be recovered from it despite forensic examination carried out in a laboratory,” they added. How the attacker reached the PLC Attacks launched directly from a PLC (the small industrial computer used to control physical equipment like motors, valves, or turbines) aren’t a scenario OT investigators usually encounter. Because the damaged WAGO device provided no logs, the investigation relied on developing and testing hypotheses. The team first checked whether the PLC had been exposed directly to the internet and ruled that out by analyzing the presence of this device type within Polish IP address space during the relevant period. Investigators then learned that the device communicated with the DSO’s systems through a SIM card connected to the DSO’s private APN. To understand how the attacker reached that network, CERT Polska revisited the wind farm attacks from the same day. Illustrative diagram of the attack against the CHP plant leveraging a private APN (Source: CERT Polska) The route started at a wind farm substation, where a FortiGate device functioned as both firewall and VPN concentrator. Its VPN interface was reachable from the internet with no multi-factor authentication, and the attacker gained administrative access across the substation’s network segments once inside. That network included a Teltonika RUTX50 cellular router with two connections: a serial link to grid equipment, as the DSO’s protocol rules required, and an Ethernet port tied into the compromised internal network, a combination the DSO had never restricted. Logs recovered from the router showed the attacker logging in over SSH repeatedly through December, then tunneling from there into the DSO’s private APN. The APN is meant to isolate the equipment connected to it. Here, it let one compromised device reach another. Starting December 18, the attacker scanned the network for VNC, HTTP, and industrial protocols including S7 and Modbus, and found the WAGO PFC200 controller at the heating plant, still running default admin credentials on its web interface. SSH wasn’t enabled there by default, but the logs suggest the attacker turned it on once inside. The controller had a route into both the plant’s SCADA system and the equipment controlling its core operations, and became the attacker’s bridge into the plant 11 days before the sabotage. A week of reconnaissance Between December 18 and 25, the attacker scanned the plant’s network and tried, without success, to log into its firewall using the account names “admin,” “user,” and a third username associated with a company that deployed telecontrol systems. Port scans covered remote access services such as RDP and VNC alongside industrial protocols. In one subnet, scanning started at the SCADA system’s IP address, which CERT Polska said suggests the attacker may have identified high-value targets during earlier reconnaissance. On Christmas Day, the attacker connected to three Siemens PLCs over the S7 protocol. The purpose of those sessions could not be determined. CERT Polska considers reconnaissance of the controllers in preparation for the disruptive actions that followed the most likely explanation. The sabotage The attack began around 5:30 a.m. on December 29. The attacker tunneled through the WAGO controller, opened the SCADA web interface, then connected in turn to a Siemens S7-300, an S7-1200, and an S7-1500, switching each into STOP mode and locking them with a password. That halted the turbine and the water treatment system. According to plant personnel, the PLCs were switched to STOP mode and protected with a password that prevented changes to their operating state and control logic. Plant staff began recovery while the attacker was still active in the network. Operators restored the affected PLCs to factory settings and reloaded available backups of their control logic. This helped reduce the duration of the outage but also erased logs stored on the controllers. Siemens ProductCERT confirmed the logs could not be recovered. The attacker also targeted seven Moxa serial device servers and three Moxa network switches, restoring them to factory settings, changing their passwords and assigning unreachable IP addresses such as 127.0.0.1. Based on the timing of the HTTP requests, CERT Polska concluded “with a high degree of confidence” that these actions were automated. Covering tracks The attacker’s activity inside the plant network ran nearly five hours, ending with one last look at the SCADA interface, likely to check the damage. They then corrupted the WAGO controller’s partition table, leaving it unable to boot, the same device CERT Polska would later strip down in the lab without recovering anything from it. Back at the wind farm, the attacker reset the Teltonika router to factory settings, then changed its administrator password and set its IP address to 127.0.0.1 to block reconfiguration. Last, they wiped the FortiGate device that had given them their original foothold, destroying its logs too. CERT Polska rebuilt the sequence by working backward from what evidence remained, since the attacker had deliberately erased so much of the trail. “To the best of our knowledge, the incident described in this report, which involved gaining access to an OT network through a private APN, was the first observed instance of this attack vector being used in a real-world cyberattack,” the researchers concluded. “Its execution was made possible, among other factors, by a misconfiguration that allowed connections to be established between arbitrary devices within the private APN network,” they added. “Based on surveys conducted with multiple entities using this type of solution, it was determined that such a configuration was commonly encountered in Poland at the time the surveys were carried out. To the best of our knowledge, similar configurations are also widely deployed in other countries around the world.”
helpnetsecurity.comAug 11, 2026extracted
Hackers breached a small Polish energy plant via private APN last year
Hackers used a dedicated mobile gateway to compromise a second facility during the destructive cyberattacks that hit Poland's energy sector last year. The second target was a small combined heat-and-power (CHP) plant that supplies heat to around 50,000 residents, resulting in the steam turbine and the water treatment system being shut down. The Polish Computer Emergency Response Team (CERT) disclosed this second incident in a follow-up report over the weekend, saying that the attacker used a private Access Point Name (APN) to access the operational technology network. "The attack was made possible, among other factors, by a misconfiguration that allowed arbitrary devices within the private APN network to communicate with one another." On December 29, 2025, an attacker believed to be linked to the Russian Electrum threat group targeted 30 wind and solar power installations and a large CHP plant in Poland, destroying key equipment beyond repair. The threat actor hit distributed energy resource (DER) sites across the country, disabled communications equipment, corrupted operational technology (OT) devices, and wiped Windows systems. Despite this effort to destabilize the grid, energy generation and distribution were not disrupted. In the newly disclosed attack at a second, smaller CHP plant, the threat actor switched off the programmable logic controllers (PLC) and protected access with a password, thus deactivating a steam turbine and the plant’s process-water treatment system and interrupting cogeneration operations. The staff at the plant managed to restore impacted systems quickly, so the outage was short-lived and had no impact on the population. Novel attack path Upon investigating the incident, the Polish CERT determined that the attacker initially compromised a FortiGate VPN/firewall at a wind farm and used a Teltonika cellular router on its network to tunnel into a private APN managed by the distribution system operator. The APN lacked client isolation, allowing the attacker to scan for and communicate with devices at other facilities. Beginning on December 18, the attacker found a WAGO PFC200 PLC at the CHP plant whose web interface was exposed on the APN and protected with default administrator credentials. After compromising the controller, the attacker enabled SSH and used it as a bridge into the plant’s OT network. Over the following week, they scanned the network for SCADA systems and industrial devices, and on December 25 they connected to three Siemens PLCs, likely in preparation for the attack. At approximately 5:30 a.m. on December 29, the attacker accessed the SCADA interface and Siemens PLCs, switching them into STOP mode, activating password protection, and shutting down the steam turbine and process-water treatment system. The attacker also reset and reconfigured several Moxa devices to impede recovery, destroyed logs, and hindered forensic analysis by corrupting or resetting the WAGO controller, Teltonika router, and FortiGate firewall used throughout the intrusion. The Polish CERT believes this to be the first known real-world cyberattack in which an attacker entered an OT network by moving laterally through a private APN. “To the best of our knowledge, the incident described in this report, which involved gaining access to an OT network through a private APN, was the first observed instance of this attack vector being used in a real-world cyberattack,” commented CERT Polska. The surveys that followed the investigation determined that this configuration was common in Poland at the time, and the country's CERT estimates that it's likely similar arrangements are widely used internationally. It is recommended to treat private APNs as untrusted external networks, enable isolation between connected clients, use allowlists for essential traffic between APN gateways and OT systems, and disable exposed SSH and Telnet administration services. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comAug 10, 2026extracted
Novel Private APN Pivot Let Hackers Sabotage Second Polish Energy Facility
Poland’s computer emergency response team (CERT) has published a report detailing a second attack on the country’s power grid. The attackers targeted industrial control systems (ICS) and their objective was “purely destructive”. In late December 2025, threat actors linked to the Russian government, specifically the APT named Sandworm, targeted communication and control systems at roughly 30 sites, including combined heat and power (CHP) plants and renewable energy dispatch centers for wind and solar facilities. In that attack, the hackers gained access to ICS, but mainly targeted grid safety and stability monitoring systems rather than active power generation systems. While some ICS devices were permanently damaged, the attack did not cause any electrical outages. In a report published over the weekend, CERT.PL revealed that the country’s energy sector was targeted in a second attack in December 2025. An investigation revealed that this attack, conducted in parallel with the previously disclosed hack, was aimed at a smaller CHP plant supplying heat to 50,000 residents. The Polish CERT’s report highlights that this appears to be the first time threat actors used a private APN as an attack vector, warning that the same vulnerable configuration has been commonly encountered in Poland and other countries around the world. The cyberattack caused the shutdown of a steam turbine and a water treatment system, which resulted in a disruption of the cogeneration process. However, the systems were quickly restored, and heat and electricity supply were not interrupted. The attack occurred during maintenance work, and it was initially believed that an engineering error had led to the disruption, but the CERT soon determined that it was the result of hacker activity. From an edge device to an energy facility’s OT network The intrusion started on a Fortinet VPN and firewall device located at a wind farm and connected to the internet. The hackers then identified a Teltonika cellular router on the same network and accessed its admin interface. An SSH service running on the device was then used to establish a tunnel that enabled communication to a private APN network managed by the distribution system operator (DSO). These private APN networks enable communication between the DSO’s SCADA system and ICS installed at the substation. The attacker scanned the private APN network and identified a Wago programmable logic controller (PLC) running at a CHP plant. An SSH service enabled on this controller gave the attacker access to the plant’s operational technology (OT) networks. After conducting reconnaissance over the course of one week, the threat actor connected to Siemens PLCs, switched them to ‘stop’ mode, and set a password to prevent operators from changing the controllers’ operating state and control logic. These actions caused the shutdown of the steam turbine and water treatment systems. Staff managed to limit the downtime by resetting the affected PLCs to their factory settings and reloading logic from backups. Moxa serial device servers and Moxa network switches were also targeted by the attackers and configured to prevent the legitimate operators from accessing them. ABB and Schneider Electric variable frequency drives were also targeted by the attackers, but it’s unclear what actions they carried out on these devices, and some attempts to connect to them were unsuccessful. Similar to the attack on the first energy facility, the hackers bricked some of the compromised ICS devices. According to the Polish CERT, some devices were permanently damaged as part of the attackers’ attempts to cover their tracks. “The attacker then damaged the WAGO controller that had been used as a gateway into the network by corrupting its partition table, preventing it from being read by the device. In an attempt to restore the controller, the affected entity performed a factory reset; however, this did not repair the partition table and the device remained unable to boot. No valuable logs could be recovered from the device during the investigation.” Related: Truck Brake Controller’s Safety Recall Doubled as Hidden Security Fix Related: Water Sector Cyberattacks Reportedly Hit at Least 12 States
securityweek.comAug 10, 2026extracted
ICS Patch Tuesday: Vulnerabilities Fixed by Siemens, Schneider, Rockwell
Industrial giants Siemens, Schneider Electric, and Rockwell Automation have published July 2026 Patch Tuesday advisories to inform customers about vulnerabilities found in their ICS products. Siemens published nine new advisories, including six that cover critical vulnerabilities (based on CVSS score). A CVSS score of 10 has been assigned to a token invalidation vulnerability in Opencenter X that allows an attacker to bypass authentication and gain full access to the application. Critical vulnerabilities have also been patched or mitigated by Siemens in Mendix, Sidis Secured SmartPlug, Simatic S7-1500, Cadra, and Desigo CC. The security holes, many of which affect third-party components, can be exploited to launch DoS attacks, execute code, obtain sensitive data, and escalate privileges. Siemens addressed high-severity vulnerabilities in Simatic S7-PLCSIM, Ruggedcom APE1808, Comos, Designcenter, Simcenter, Solid Edge, and Tecnomatrix products. Schneider Electric has released two new advisories. One of them addresses a high-severity vulnerability in the IGSS (Interactive Graphical SCADA System) product. An attacker can use specially crafted files to execute arbitrary code. The second advisory describes a high-severity authentication bypass flaw in EcoStruxure Cybersecurity Admin Expert that can be exploited by a local attacker to compromise managed devices. Rockwell Automation published 12 new advisories on Tuesday, including two covering critical vulnerabilities. A critical vulnerability in the 1715 Redundant IO product can allow an unauthenticated attacker to access intrusive CLI commands, enabling them to read or delete files, stop tasks, change IO states, and modify memory. Three critical DoS security holes that can be exploited to cause a major non-recoverable fault have been patched by Rockwell in its CompactLogix, ControlLogix, Compact GuardLogix, and GuardLogix controllers. Rockwell patched high-severity vulnerabilities in Flex 5000 Adapter, FactoryTalk DataMosaix, FactoryTalk Services Platform, Arena, ThinManager, Studio 5000 Logix Designer, 1756-EN, 1734 POINT I/O, and 1719-AENTR products. ABB and Mitsubishi Electric have not published any new advisories this Patch Tuesday, but they have informed customers of new flaws over the past month, including critical and high-severity issues. Three ABB advisories and one Rockwell advisory were also distributed by the cybersecurity agency CISA on Tuesday. Germany’s VDE CERT has published five new advisories covering vulnerabilities in Murrelektronik, Mettler Toledo, Codesys, and Wago products. Related: ICS Patch Tuesday: Vulnerabilities Fixed by Siemens, Schneider, Phoenix Contact Related: ICS Patch Tuesday: 8 Industrial Giants Publish New Security Advisories
securityweek.comJul 15, 2026extracted
ICS Patch Tuesday: 8 Industrial Giants Publish New Security Advisories
Industrial giants Siemens, Schneider Electric, Aveva, Rockwell Automation, ABB, Phoenix Contact, Mitsubishi Electric, and Moxa have published new ICS security advisories since the previous Patch Tuesday. Siemens has published nine new advisories since the previous Patch Tuesday. Vulnerabilities with a ‘critical’ severity rating are mentioned only in one advisory covering older Wi-Fi vulnerabilities affecting Scalance W-700 devices. Siemens has addressed high-severity vulnerabilities in Sinec NMS (authentication/authorization bypass), Ruggedcom Crossbow (privilege escalation, code execution, DoS), and Industrial Edge Management (authorization bypass). Medium-severity issues have been resolved in TPM and Analytics Toolkit. The company also announced that it’s participating in the CVE Program’s new Supplier Authorized Data Publisher (SADP) project, which enables vendors such as Siemens to add information to vulnerability entries. Cisco, Microsoft, HeroDevs, Oracle, and Red Hat also took part in the SADP pilot. Schneider Electric has published three new advisories. One of them describes the impact of the BlastRadius vulnerability disclosed in 2024 on the company’s Modicon Networking Managed Switch. The other two advisories cover medium-severity vulnerabilities in the PowerChute Serial Shutdown UPS management software and Easergy MiCOM Px40 protection relays. Aveva released an advisory to inform customers about a critical missing authorization and privilege escalation vulnerability in Pipeline Simulation. Since the last Patch Tuesday, Rockwell Automation published an important notice urging customers to disconnect PLCs from the internet after becoming aware of potential threat actor activity. The alert is likely related to the attacks conducted by Iran-linked threat groups against critical infrastructure organizations via PLC hacking. ABB has issued four advisories since the previous Patch Tuesday. Three of them cover third-party component vulnerabilities in Ability Camera Connect, Ability Symphony, and System 800xA products. The last advisory describes a DoS vulnerability in the System 800xA and Symphony Plus IEC 61850 communication stack. Phoenix Contact has one new advisory that informs customers about multiple flaws in FL Switch products. Mitsubishi Electric released two new advisories: one for a DoS vulnerability introduced by Realtek chips in home appliances; and one for multiple information disclosure, tampering, and DoS flaws in Genesis64, Iconics Suite, MobileHMI, Hyper Historian, AnalytiX, and MC Works64 products. Moxa has a new advisory covering an MxGeneralIo security hole that can lead to DoS or privilege escalation. Since the previous Patch Tuesday, CISA has published advisories for vulnerabilities in GPL Odorizers, Contemporary Controls, Mitsubishi Electric, Hitachi Energy, Yokogawa, PX4, Anritsu, PTC, OpenCode Systems, Wago, Pharos, Grassroots, Automated Logic, IGL-Technologies, CTEK, Codesys, and Inductive Automation products. Germany’s CERT@VDE has released advisories for Codesys, MB Connect Line, Helmholz, Wago, Phoenix Contact, Baade M2M-Products, and Endress+Hauser products.
securityweek.comApr 15, 2026extracted
ICS Patch Tuesday: Vulnerabilities Addressed by Siemens, Schneider, Aveva, Phoenix Contact
Industrial giants Siemens, Schneider Electric, Aveva, and Phoenix Contact have published Patch Tuesday advisories informing customers about vulnerabilities found in their ICS/OT products. Siemens has published eight new advisories. The company has released patches and mitigations for high-severity issues in Desigo CC, Sentron Powermanager, Simcenter Femap and Nastran, NX, Sinec NMS, Solid Edge, and Polarion products. A medium-severity flaw has been found in Siveillance Video Management Servers. Exploitation of the vulnerabilities can lead to unauthorized access, XSS, DoS, code execution, and privilege escalation. Siemens has also released an advisory that describes the lack of anti-tamper protections and modern exploit mitigation controls in the Siport desktop client application. “As a result, the application is susceptible to unauthorized modification and potential abuse,” the company explained. Schneider Electric published two new advisories. One describes two high-severity flaws that can lead to DoS, information disclosure, or code execution in EcoStruxure Building Operation Workstation and WebStation. The second advisory describes a critical issue that can result in DoS or code execution on SCADAPack RTUs. Aveva has informed customers about a high-severity DoS vulnerability in PI Data Archive and a medium-severity unauthorized access issue in PI to Connect Agent. Phoenix Contact has released an advisory to address a 2024 OpenSSL vulnerability. The advisory was also picked up by Germany’s VDE CERT, which also published an advisory for Wago managed switch flaws. CISA published five new advisories on Patch Tuesday. They describe vulnerabilities in Yokogawa Fast/Tools, Zlan ZLAN5143D, and the Zoll ePCR mobile application, as well as the Aveva issues disclosed on Tuesday In the days leading up to Patch Tuesday, advisories were published by Mitsubishi Electric for vulnerabilities in Freqship-mini for Windows and Melsec iQ-R, and by Moxa for security holes in industrial computers and switches. Related: ICS Patch Tuesday: Vulnerabilities Fixed by Siemens, Rockwell, Schneider
securityweek.comFeb 11, 2026extracted
ICS Patch Tuesday: Rockwell Automation Leads With 8 Security Advisories
Several industrial control systems (ICS) giants have published new security advisories this Patch Tuesday, including Rockwell Automation, Siemens, Schneider Electric, and Phoenix Contact. Rockwell Automation published the highest number of new advisories this Patch Tuesday. The company released eight new advisories, all of them covering high-severity vulnerabilities found recently in the company’s products. Rockwell fixed a sensitive data exposure issue in FactoryTalk Analytics LogixAI, and DoS and code execution issues in ControlLogix controllers. It also addressed a remote code execution vulnerability in Stratix (Cisco) devices, a memory corruption in 1783-NATR, a SSRF issue in Automation ThinManager, a remote code execution flaw in FactoryTalk Optix, and a data exposure issue in FactoryTalk Activation Manager. Siemens has published seven new advisories. With a CVSS score of 9.3, one of the most serious issues impacts Simatic Virtualization as a Service and allows an attacker to access or alter sensitive data. Another vulnerability with a ‘critical’ severity rating impacts Siemens’ User Management Component (UMC) and it can be exploited for unauthenticated remote code execution or DoS attacks. Siemens also addressed high-severity issues in Simotion and Industrial Edge Management products. Advisories covering medium- and low-severity flaws have been published for Sinamics, Apogee PXC and Talon TC, and Sinec OS products. Schneider Electric published only two new advisories this Patch Tuesday. One of them covers two medium-severity OS command injection issues in Saitel DR & Saitel DP RTU products. The second advisory informs customers about an XSS flaw in Altivar products. Phoenix Contact has published two new advisories: one for two vulnerabilities in the Jq JSON processor used by FL Mguard, and one for a vulnerability introduced by the use of Wibu’s CodeMeter Runtime. Honeywell has published several advisories for building management products, including Maxpro and Pro-Watch NVR and VMS products. CISA has published nine new and five updated advisories. Of the new advisories, a vast majority cover the Rockwell Automation product vulnerabilities. One CISA advisory informs organizations about ABB product vulnerabilities. The vendor published its own advisory for the flaws, which impact its Aspect building management system, earlier this month. The issues were reported to ABB by researcher Gjoko Krstic, who in January claimed to have found over 1,000 vulnerabilities in ABB products. Germany’s CERT@VDE agency published seven new advisories this week, including for a critical Wago controller vulnerability that can be exploited without authentication for DoS attacks and to weaken credentials, resulting in default credentials being applied to the device. CERT@VDE’s advisories also cover two other Wago product vulnerabilities, two Bender Charge Controller issues, and the recently disclosed Phoenix Contact flaws. Related: ICS Patch Tuesday: Major Vendors Address Code Execution Vulnerabilities
securityweek.comSep 10, 2025extracted