Siemens Simcenter Femap heap overflow via malicious IPT files
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Heap buffer overflow in Siemens Simcenter Femap allows remote code execution when opening specially crafted IPT files.
Siemens Simcenter Femap is affected by a heap-based buffer overflow vulnerability in its Datakit library that is triggered when the application parses IPT format files. An attacker could exploit this by crafting a malicious IPT file and tricking a user into opening it, leading to remote code execution in the context of the application's process. The vulnerability affects Simcenter Femap versions prior to 2512.0003. Siemens has released a patched version and recommends immediate update. This vulnerability was reported by TrendAI through the Zero Day Initiative and has been assigned CVE-2025-12659. The flaw is rooted in improper bounds checking during memory operations on heap buffers, classified as CWE-122. There is no indication the vulnerability is currently exploited in the wild; this is a proactive vendor advisory with an available patch.
Mentioned in this report
Detection guidance
Siemens Femap Spawning Shell or Script Interpreter
Femap (femap.exe) spawning a command shell, script host or LOLBin, which is consistent with code execution after a malicious IPT file triggers the Datakit heap overflow (CVE-2025-12659). Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Siemens Femap Spawning Shell or Script Interpreter
description: Detects femap.exe spawning a command shell, script host or common living-off-the-land
binary. Femap does not normally launch these, so a child like this after opening
a CAD file such as an IPT is consistent with exploitation of the Datakit heap overflow
(CVE-2025-12659).
status: experimental
tags:
- attack.execution
- attack.t1204.002
- attack.t1190
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
- \msiexec.exe
- \curl.exe
condition: selection_parent and selection_child
falsepositives:
- Femap analysis or solver launch scripts or add-ins that call cmd.exe to run batch
files
- Custom engineering macros or API scripts that shell out from Femap
level: medium
id: e3b6943e-fb8e-5f30-85d7-96d98c01b46d
author: Vorant
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-134-05
Femap Launched With IPT File From User-Writable or Download Location
femap.exe started with an .ipt file argument from Downloads, Temp or mail/archive extraction paths, the delivery pattern for a malicious IPT file opened by a user. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Femap Launched With IPT File From User-Writable or Download Location
description: Detects femap.exe launched with an .ipt file located in a download, temp
or mail-attachment path. This is the user-execution step for a crafted IPT file
exploiting CVE-2025-12659. Intended as a low-severity hunting or context rule to
correlate with child-process alerts.
status: experimental
tags:
- attack.execution
- attack.t1204.002
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith: \femap.exe
CommandLine|contains: .ipt
selection_path:
CommandLine|contains:
- \Downloads\
- \AppData\Local\Temp\
- \Content.Outlook\
- \INetCache\
- \Temp\7z
- \Temp\Rar
condition: selection and selection_path
falsepositives:
- Engineers legitimately opening IPT models received from colleagues or suppliers
and saved to Downloads
- Users opening IPT attachments directly from email
level: low
id: 9e84c2b0-29ab-505e-9539-7cb4e06b35f0
author: Vorant
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-134-05
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-26-134-05
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 614 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs