Schneider Electric has released a critical security advisory (ICSA-26-211-04) addressing a severe vulnerability within the IGSS (Interactive Graphical SCADA System) Definition module. Affected versions include IGSS Definition (Def.exe) versions 18.0.0.26124 and earlier, as well as 18.0.0.26125.
For organizations utilizing IGSS in critical infrastructure environments, the stakes are high. Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code, leading to a complete loss of data and, crucially, a loss of control over the industrial processes monitored by the SCADA system. As this component is used during the design phase to create mimic diagrams, it represents a prime vector for initial access via maliciously crafted project files or supply-chain compromise of engineering workstations.
Technical Analysis
Affected Component: The vulnerability resides specifically in Def.exe, the IGSS Definition module. This component is a design-time tool used by system integrators and engineers to build the HMI mimic diagrams and logic configurations.
Affected Versions:
- IGSS Definition (Def.exe) module versions <= 18.0.0.26124
- IGSS Definition (Def.exe) module version 18.0.0.26125
Vulnerability Mechanism: While specific technical details (CVE) are pending broader disclosure, the advisory warns of arbitrary code execution. In SCADA design environments, this often points to a memory corruption vulnerability (e.g., buffer overflow or use-after-free) triggered when parsing specific data structures within project files or diagram definitions. Because Def.exe typically runs with elevated privileges to interact with low-level drivers or configure system services, the exploit context allows for immediate system compromise.
Risk Impact:
- Loss of Control: Arbitrary code execution on an engineering workstation can be pivoted to the SCADA server, allowing attackers to alter process logic.
- Data Integrity: Manipulation of historical data or configuration databases.
- Lateral Movement: Engineering workstations often bridge the IT/OT gap; compromising
Def.exeprovides a foothold to move deeper into the ICS network.
Detection & Response
Detecting exploitation of design-time modules requires monitoring for anomalies in process behavior rather than network traffic, as the attack vector is likely file-based or local.
Sigma Rules
The following Sigma rule detects suspicious child process spawns from the Definition module, a strong indicator of successful code execution.
---
title: Schneider Electric IGSS Definition Module Spawning Shell
id: a1b2c3d4-2626-4e8a-a1b2-3f4a5b6c7d8e
status: experimental
description: Detects the IGSS Definition module (Def.exe) spawning cmd.exe, powershell.exe, or other shells. This behavior is highly anomalous for a design-time tool and indicates potential exploit activity.
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-211-04
author: Security Arsenal
date: 2026/05/06
tags:
- attack.execution
- attack.t1203
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: '\Def.exe'
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
condition: selection
falsepositives:
- Legitimate administrative scripting initiated by the operator (unlikely)
level: high
---
title: Schneider Electric IGSS Definition Module Unusual Network Connection
id: b2c3d4e5-2626-4e8a-b2c3-4a5b6c7d8e9f
status: experimental
description: Detects outbound network connections initiated by Def.exe. The definition module is a local design tool and should not initiate network connections on its own.
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-211-04
author: Security Arsenal
date: 2026/05/06
tags:
- attack.command_and_control
- attack.t1071
logsource:
category: network_connection
product: windows
detection:
selection:
Image|endswith: '\Def.exe'
Initiated: 'true'
condition: selection
falsepositives:
- Vendor software update checks or license verification (rare)
level: medium
KQL (Microsoft Sentinel / Defender)
Use these queries to hunt for vulnerable versions or behavioral indicators on your endpoints.
// Hunt for vulnerable versions of Def.exe in the environment
DeviceFileEvents
| where FileName =~ "Def.exe"
| extend FileVersion = tostring(parse_(AdditionalFields).FileVersion)
| where FileVersion in~ ("18.0.0.26124", "18.0.0.26125") or FileVersion < "18.0.0.26124"
| project Timestamp, DeviceName, FolderPath, FileVersion, SHA256
| order by Timestamp desc
// Hunt for suspicious process creation by Def.exe
DeviceProcessEvents
| where InitiatingProcessFileName =~ "Def.exe"
| where ProcessFileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "regsvr32.exe", "rundll32.exe")
| project Timestamp, DeviceName, AccountName, InitiatingProcessVersionInfoCompanyName, FileName, ProcessCommandLine, ActionType
| order by Timestamp desc
Velociraptor VQL
This artifact hunts for the presence of the vulnerable executable on disk.
-- Hunt for vulnerable IGSS Definition Module versions
SELECT FullPath, Size, Mtime, parse_string(FileVersion=Version.String) AS FileVersion
FROM glob(globs="C:/Program Files*/**/Def.exe")
WHERE FileVersion =~ "18.0.0.26124"
OR FileVersion =~ "18.0.0.26125"
OR parse_version(FileVersion) < parse_version("18.0.0.26124")
Remediation Script (PowerShell)
Run this script on engineering workstations to identify if the vulnerable module is present.
# Audit Script for Schneider Electric IGSS Definition Module (ICSA-26-211-04)
# Identifies vulnerable versions of Def.exe
$VulnerableVersions = @("18.0.0.26124", "18.0.0.26125")
$BasePaths = @("C:\Program Files", "C:\Program Files (x86)")
$FoundVulnerable = $false
foreach ($Path in $BasePaths) {
if (Test-Path $Path) {
$Files = Get-ChildItem -Path $Path -Filter "Def.exe" -Recurse -ErrorAction SilentlyContinue
foreach ($File in $Files) {
$VersionInfo = $File.VersionInfo
$FileVersion = $VersionInfo.FileVersion
# Check if version is in the specific vulnerable list or older than the fixed version
if ($VulnerableVersions -contains $FileVersion -or $FileVersion -lt "18.0.0.26126") {
Write-Host "[ALERT] Vulnerable IGSS Definition Module found: $($File.FullName)" -ForegroundColor Red
Write-Host "Version: $FileVersion" -ForegroundColor Red
$FoundVulnerable = $true
}
}
}
}
if (-not $FoundVulnerable) {
Write-Host "No vulnerable IGSS Definition modules found on this host." -ForegroundColor Green
}
Remediation
To mitigate the risks associated with ICSA-26-211-04, follow these steps immediately:
- Apply Vendor Patch: Schneider Electric has released a remediation for this vulnerability. Update the IGSS Definition module to the latest version provided by the vendor. Ensure the target version is newer than 18.0.0.26125.
- Network Segmentation: Ensure that engineering workstations hosting the IGSS Definition module are isolated from the internet and strictly segmented from the control plane network via a DMZ or jump host.
- Restrict File Sharing: Disable the sharing of untrusted project files (
.igss,.def) via email or external drives. Validate all project files in a sandbox environment before importing into the production design environment. - Principle of Least Privilege: Ensure operators and engineers do not run the Definition module with administrative domain credentials unless absolutely necessary.
Official Advisory: CISA ICSA-26-211-04
Related Resources
Security Arsenal Managed SOC Services AlertMonitor Platform Book a SOC Assessment soc-mdr Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.