CISA has published ICS advisory ICSA-26-225-11 covering two file-parsing vulnerabilities in Siemens Simcenter Femap, the finite element analysis (FEA) pre/post-processor used heavily across critical manufacturing, aerospace, automotive, and defense engineering environments. Both flaws — an out-of-bounds read and a companion parsing defect — are triggered when Femap processes a maliciously crafted BMP image file. A successful attack requires social engineering: convincing an engineer to open a weaponized file inside the affected application.
The outcome ranges from application crash to arbitrary code execution in the context of the logged-on user. Femap carries a CVSS v3 score of 7.8 (High), and Siemens has released a fixed version. If your organization runs engineering workstations with Femap installed — and in critical manufacturing, that is nearly guaranteed — this advisory belongs on this week's patch queue.
Why This Matters to Defenders
Engineering workstations are among the most sensitive and least monitored assets in industrial environments. They hold CAD models, simulation data, and intellectual property, they frequently bridge IT and OT networks, and they run software that rarely appears in EDR coverage policies. A code-execution primitive delivered through a "harmless" BMP attachment to an engineer's inbox is exactly the kind of initial access vector that nation-state and espionage-motivated actors favor — the file format is ubiquitous, the target user is privileged, and the host often has network paths into both corporate and plant-side systems.
The exploitation requirement (user opens a file) does not diminish severity. It defines the detection strategy: watch the application process for anomalous behavior after file-open events, and gate the delivery channel (email, file shares, PLM/team collaboration systems) that would carry the malicious BMP.
Technical Analysis
Affected Products and Versions
| Product | Affected Versions | Fixed Version |
|---|---|---|
| Siemens Simcenter Femap | All versions < 2606.0001 | 2606.0001 and later |
- CVE-2026-59700 — Out-of-bounds read in BMP file parsing
- CVE-2026-59701 — Second BMP parsing defect (same attack surface, companion flaw addressed in the same release)
- CVSS v3: 7.8 (High) — Local attack vector, user interaction required, high confidentiality/integrity/availability impact
- Critical infrastructure sectors: Critical Manufacturing
- Deployment: Worldwide (vendor headquartered in Germany)
How the Vulnerability Works
Femap parses BMP images when they are imported or embedded into model files, reports, or documentation views. The vulnerable parsing routine reads BMP header fields (dimensions, bit depth, offset tables) without adequately validating them against the actual buffer size. A crafted BMP declares dimensions or offsets that cause the parser to read beyond the allocated buffer boundary — the classic out-of-bounds read condition.
From a defender's perspective, the attack chain looks like this:
- Delivery: Attacker sends or stages a malicious
.bmpfile — email attachment, shared network drive, PLM system, or bundled inside an engineering archive. - Trigger: Engineer opens or imports the file in Femap (or opens a model that references it).
- Exploitation: The OOB read corrupts the parsing routine's memory state. At minimum, Femap crashes (denial of engineering availability). With additional heap grooming, the read primitive can be chained into arbitrary code execution under the engineer's user context.
- Post-exploitation: The attacker's payload inherits the engineer's privileges — typically local admin on an engineering workstation, with access to design IP and network segments reaching OT.
Exploitation Status
As of the advisory publication, there is no confirmed in-the-wild exploitation and neither CVE appears in the CISA Known Exploited Vulnerabilities catalog. No public proof-of-concept has been reported. Treat this as a window of opportunity, not a reason to defer: ICS advisories for engineering software consistently attract reverse-engineering attention within weeks, and the vulnerability class (image parsing OOB read) is well understood by exploit developers.
Detection & Response
Because exploitation manifests as abnormal behavior by the Femap process itself (crash, unexpected child processes, network connections), endpoint telemetry on engineering workstations is your primary detection plane. The detections below target observable post-exploitation behavior rather than the BMP file bytes themselves — file-content signatures would be speculative at this stage, while process-behavior analytics are reliable regardless of the specific exploit construction.
Sigma Rules
---
title: Siemens Simcenter Femap Spawning Child Process
description: Detects the Femap application spawning a child process, which may indicate successful exploitation of CVE-2026-59700 or CVE-2026-59701 via a malicious BMP file. Femap does not legitimately spawn shells, script interpreters, or Office applications.
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-225-11
- https://attack.mitre.org/techniques/T1203/
author: Security Arsenal
date: 2026/08/13
status: experimental
id: 8f2a1c44-3d7b-4e91-b6a2-5c9d0e1f2a3b
tags:
- attack.execution
- attack.t1203
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\femap.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
- '\certutil.exe'
- '\bitsadmin.exe'
- '\wmic.exe'
condition: selection_parent and selection_child
falsepositives:
- Rare; Femap may invoke licensed solver binaries, which should be excluded by path once observed
level: high
---
title: BMP File Written to Engineering Workstation Temp or Email Cache
description: Detects BMP image files being written to temporary, email cache, or download directories on systems where Femap is installed, a common delivery staging pattern for CVE-2026-59700/CVE-2026-59701 malicious file attacks. Tune to your environment's file-delivery paths.
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-225-11
- https://attack.mitre.org/techniques/T1566.001/
author: Security Arsenal
date: 2026/08/13
status: experimental
id: 2b7e9d15-6a4c-4f38-9d01-8e3b5c7a9f24
tags:
- attack.initial_access
- attack.t1566.001
logsource:
category: file_event
product: windows
detection:
selection_ext:
TargetFilename|endswith: '.bmp'
selection_path:
TargetFilename|contains:
- '\AppData\Local\Temp\'
- '\Downloads\'
- 'Content.Outlook\'
- '\INetCache\'
filter_known_apps:
Image|endswith:
- '\msedge.exe'
- '\chrome.exe'
condition: selection_ext and selection_path and not filter_known_apps
falsepositives:
- Screenshot tools and legacy document workflows that export BMP files; exclude known exporter binaries
level: medium
---
title: Siemens Femap Application Crash Followed by Suspicious Execution
description: Detects a Femap crash event followed by execution of a command shell or script interpreter on the same host within a short window, consistent with exploitation of CVE-2026-59700/CVE-2026-59701 where an attacker payload stabilizes after a parsing crash.
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-225-11
- https://attack.mitre.org/techniques/T1203/
author: Security Arsenal
date: 2026/08/13
status: experimental
id: 4c6d8f02-1b3a-4e59-a7c4-9d2e6f8a0b15
tags:
- attack.execution
- attack.t1203
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- '\WerFault.exe'
- '\werfaultsecure.exe'
CommandLine|contains:
- 'femap.exe'
condition: selection
falsepositives:
- Genuine Femap instability from oversized models; investigate any crash co-occurring with new BMP files on the host
level: medium
KQL — Microsoft Sentinel / Defender
The following hunt queries assume Defender for Endpoint (or equivalent) coverage on engineering workstations. The first targets Femap spawning any unusual child process; the second correlates BMP file delivery with Femap execution on the same device.
// Hunt 1: Femap spawning suspicious child processes (post-exploitation behavior)
DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where InitiatingProcessFileName =~ "femap.exe"
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe",
"cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe", "certutil.exe",
"bitsadmin.exe", "wmic.exe", "msiexec.exe")
| project TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine,
InitiatingProcessCommandLine, InitiatingProcessFolderPath, ReportId
| order by TimeGenerated desc
// Hunt 2: BMP files staged in delivery directories, correlated with Femap on the same host
let BmpHosts =
DeviceFileEvents
| where TimeGenerated > ago(14d)
| where FileName endswith ".bmp"
| where FolderPath has_any ("\\Downloads\\", "\\Temp\\", "Content.Outlook", "INetCache")
| summarize BmpCount = count(), BmpFiles = make_set(FileName, 20),
FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated)
by DeviceName, InitiatingProcessFileName;
BmpHosts
| join kind=inner (
DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where FileName =~ "femap.exe"
| summarize FemapRuns = count() by DeviceName
) on DeviceName
| project DeviceName, BmpCount, BmpFiles, InitiatingProcessFileName,
FemapRuns, FirstSeen, LastSeen
| order by BmpCount desc
// Hunt 3: Femap application crashes (WerFault) as potential exploitation attempts
DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where FileName =~ "WerFault.exe"
| where ProcessCommandLine has "femap"
| project TimeGenerated, DeviceName, AccountName, ProcessCommandLine,
InitiatingProcessFileName
| order by TimeGenerated desc
Velociraptor VQL
Use this artifact to sweep your engineering workstation fleet: identify installed Femap versions below the fixed build, then enumerate any Femap child processes and recently created BMP files in staging locations.
-- Security Arsenal: Hunt for vulnerable Femap installs, suspicious child processes,
-- and staged BMP files (CVE-2026-59700 / CVE-2026-59701)
-- 1. Identify installed Femap versions from uninstall registry keys
SELECT DisplayName, DisplayVersion, InstallLocation, Key.Name AS RegKey
FROM glob(
globs='HKLM:/SOFTWARE/Microsoft/Windows/CurrentVersion/Uninstall/*/DisplayName',
accessor='registry'
)
WHERE DisplayName =~ 'Femap'
-- 2. Femap processes with unexpected children
SELECT Pid, Ppid, Name, Exe, CommandLine, Username, CreateTime
FROM pslist()
WHERE Exe =~ '(?i)femap\\.exe'
OR CommandLine =~ '(?i)femap'
-- 3. BMP files recently written to staging directories
SELECT FullPath, Size, Mtime, Atime
FROM glob(
globs=[
'C:/Users/*/Downloads/*.bmp',
'C:/Users/*/AppData/Local/Temp/*.bmp'
]
)
WHERE Mtime > (now() - 1209600)
ORDER BY Mtime DESC
Remediation and Verification Script
Run the following PowerShell (elevated) on engineering workstations to inventory Femap installations, flag vulnerable versions, and check for indicators of crash-based exploitation attempts. It does not deploy the patch — Siemens updates are distributed through the Siemens Support Center — but it gives you a fleet-wide posture snapshot and a hunting hook.
# Security Arsenal - Siemens Simcenter Femap CVE-2026-59700/59701 verification script
# Run elevated on engineering workstations
$fixedVersion = [version]"2606.0001"
$report = [ordered]@{ Host = $env:COMPUTERNAME; Installs = @(); Crashes = @(); Verdict = "UNKNOWN" }
# 1. Locate Femap installations via uninstall registry
$uninstallPaths = @(
"HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
"HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*"
)
$femapInstalls = Get-ItemProperty $uninstallPaths -ErrorAction SilentlyContinue |
Where-Object { $_.DisplayName -match "Femap" } |
Select-Object DisplayName, DisplayVersion, InstallLocation
foreach ($inst in $femapInstalls) {
$v = $null
[void][version]::TryParse(($inst.DisplayVersion -replace '[^0-9\.]', ''), [ref]$v)
$status = if ($v -and $v -lt $fixedVersion) { "VULNERABLE" } elseif ($v) { "PATCHED" } else { "VERSION-UNPARSED" }
$report.Installs += [pscustomobject]@{
Product = $inst.DisplayName
Version = $inst.DisplayVersion
Path = $inst.InstallLocation
Status = $status
}
}
# 2. Check Application event log for Femap crashes in the last 30 days
$crashes = Get-WinEvent -FilterHashtable @{ LogName = 'Application'; Id = 1000; StartTime = (Get-Date).AddDays(-30) } -ErrorAction SilentlyContinue |
Where-Object { $_.Message -match "femap" } |
Select-Object TimeCreated, Message
$report.Crashes = $crashes
# 3. Verdict
if (-not $femapInstalls) { $report.Verdict = "FEMAP-NOT-INSTALLED" }
elseif ($report.Installs.Status -contains "VULNERABLE") { $report.Verdict = "ACTION-REQUIRED: Update to Simcenter Femap 2606.0001 or later" }
elseif ($report.Installs.Status -contains "VERSION-UNPARSED") { $report.Verdict = "MANUAL-REVIEW: Could not parse installed version" }
else { $report.Verdict = "COMPLIANT" }
$report.Installs | Format-Table -AutoSize
Write-Host "`nVerdict: $($report.Verdict)" -ForegroundColor (if ($report.Verdict -match "ACTION") { "Red" } else { "Green" })
if ($report.Crashes) {
Write-Host "`nFemap crash events (last 30 days) - review for exploitation attempts:" -ForegroundColor Yellow
$report.Crashes | Format-Table TimeCreated -AutoSize
}
Remediation
-
Patch immediately. Upgrade all Simcenter Femap installations to version 2606.0001 or later. The update is available through the Siemens Support Center. Reference advisories:
- CISA ICS Advisory: https://www.cisa.gov/news-events/ics-advisories/icsa-26-225-11
- Siemens ProductCERT / CSAF feed (linked from the CISA advisory)
-
Inventory first. Femap is frequently installed outside formal software management — individual engineering licenses, lab machines, contractor laptops. Use the script above or your EDR software inventory to find every install before declaring patch complete.
-
Gate the delivery channel. Until patching is verified fleet-wide:
- Block or sandbox-detotate inbound
.bmpattachments at the email gateway for engineering distribution groups. - Alert on BMP files arriving via file shares, PLM vaults, or collaboration platforms into engineering team workspaces.
- Instruct engineers not to open BMP files from untrusted or unexpected sources, and to report crashes that occur immediately after opening an image.
- Block or sandbox-detotate inbound
-
Harden engineering workstations. These hosts warrant the same controls as any high-value asset: EDR coverage (verify Femap.exe is not excluded from process monitoring), attack surface reduction rules blocking Office/script child processes, least-privilege removal of local admin where operationally feasible, and network segmentation limiting workstation reachability to OT segments.
-
Post-patch verification. Confirm the installed build string reports 2606.0001+, review the last 30–90 days of Femap crash events on hosts that were running vulnerable versions, and treat any crash co-occurring with a newly arrived BMP file as a potential compromise warranting DFIR triage.
No CISA KEV deadline applies as of publication — but given the critical manufacturing sector designation and the trivial delivery vector, a 14-day patch SLA is appropriate for internet-adjacent engineering hosts, with compensating controls documented for anything that cannot be patched in that window.
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.