Back to Intelligence

CVE-2026-64629: Siemens Simcenter Femap Out-of-Bounds Read — Detection and Remediation Guide

SA
Security Arsenal Team
November 18, 2026
10 min read

On January 13, 2026, CISA published ICS Advisory ICSA-26-321-10 disclosing a high-severity vulnerability in Siemens Simcenter Femap, a widely deployed finite element analysis (FEA) application used in critical manufacturing environments worldwide. Tracked as CVE-2026-64629 with a CVSS v3 score of 7.8, this out-of-bounds read vulnerability affects all Simcenter Femap versions prior to 2606.0002 and can be triggered simply by opening a maliciously crafted Parasolid X_T format file.

For organizations operating in the Critical Manufacturing sector, this is not a theoretical risk. Engineering workstations running CAD/CAE software routinely exchange files with suppliers, contractors, and customers — a supply-chain attack surface that threat actors have historically abused to gain initial footholds in otherwise well-segmented environments. A successful exploit could crash the application (denial of service) or, worse, achieve arbitrary code execution in the context of the user who opened the file. Siemens has released version 2606.0002 to remediate this flaw, and immediate patching is strongly recommended.

Technical Analysis

Affected Products and Versions

ProductAffected VersionsFixed Version
Siemens Simcenter FemapAll versions < 2606.00022606.0002 and later

Vulnerability Details

CVE-2026-64629 is an out-of-bounds read (CWE-125) vulnerability residing in the file-parsing logic that Simcenter Femap uses when reading Parasolid X_T format files. The X_T format is a boundary representation (B-rep) file format used to exchange 3D CAD geometry between applications. Because Femap must parse complex geometric data structures from untrusted input, improper bounds checking during the parsing routine allows an attacker to craft a file that causes the application to read memory beyond the allocated buffer.

From a defender's perspective, the attack chain looks like this:

  1. Delivery: An attacker crafts a malicious .x_t file containing specially malformed geometric data structures.
  2. Distribution: The file is delivered to the target via email attachment, shared engineering file repositories, PLM system uploads, or any workflow where X_T files are exchanged between organizations.
  3. Trigger: A user opens the file in Simcenter Femap (or the file is processed by an automated workflow that invokes Femap's import functionality).
  4. Exploitation: The out-of-bounds read is triggered during parsing. Depending on the attacker's sophistication and the memory layout, this can result in:
    • Application crash — denial of service on the engineering workstation
    • Information disclosure — reading sensitive data from adjacent memory
    • Arbitrary code execution — if the attacker can chain the OOB read with additional techniques to control execution flow

The CVSS v3 vector is consistent with a local attack vector (AV:L) requiring user interaction (UI:R) — meaning the victim must open the malicious file. No network exposure of the application itself is required.

Exploitation Status

As of the advisory publication date, there is no confirmed in-the-wild exploitation, no public proof-of-concept code, and CVE-2026-64629 has not been added to CISA's Known Exploited Vulnerabilities (KEV) catalog. However, the vulnerability class (file-parsing memory corruption in engineering software) is a well-established attack vector. Organizations should treat this as a pre-emptive patching priority rather than waiting for active exploitation to be confirmed.

Detection & Response

The primary defensive control for this vulnerability is patching. However, because exploitation requires a user to open a malicious file, detection strategies should focus on identifying anomalous Femap process behavior, monitoring for suspicious X_T file provenance, and hunting for post-exploitation activity spawned from the Femap process.

SIGMA Rules

YAML
---
title: Siemens Femap Spawning Unexpected Child Processes
id: 3f8a2c15-7e91-4b6d-a412-8c9f0d2e5a1b
status: experimental
description: Detects Simcenter Femap (femap.exe) spawning command interpreters, script engines, or other unexpected child processes, which may indicate successful exploitation of CVE-2026-64629 via a malicious X_T file.
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-10
  - https://attack.mitre.org/techniques/T1203/
author: Security Arsenal
date: 2026/01/16
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'
  condition: selection_parent and selection_child
falsepositives:
  - Rare — Femap does not normally spawn command interpreters or script engines
  - Custom automation scripts integrated with Femap may trigger; whitelist known workflows
level: high
---
title: Femap Process Crash Indicating Possible Exploitation Attempt
id: 8b2d4e67-1a3f-4c58-9d71-2e6b8a4c5d3f
status: experimental
description: Detects application error or crash events associated with femap.exe, which may indicate an attempted or successful exploitation of the out-of-bounds read vulnerability (CVE-2026-64629) via a malformed X_T file.
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-10
author: Security Arsenal
date: 2026/01/16
tags:
  - attack.impact
  - attack.t1499
logsource:
  product: windows
  service: application
detection:
  selection:
    Message|contains:
      - 'femap.exe'
    EventSourceName:
      - 'Application Error'
      - 'Application Hang'
      - 'Windows Error Reporting'
  condition: selection
falsepositives:
  - Femap may crash during normal operations on complex models; correlate with X_T file access timing
level: medium

KQL Hunt Query (Microsoft Sentinel / Defender)

KQL — Microsoft Sentinel / Defender
// Hunt for Femap process anomalies and child process execution
// Target: CVE-2026-64629 post-exploitation behavior
let SuspiciousChildren = dynamic([
    "cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe",
    "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe",
    "certutil.exe", "bitsadmin.exe", "msiexec.exe"
]);
DeviceProcessEvents
| where TimeGenerated > ago(30d)
| where InitiatingProcessFileName =~ "femap.exe"
| where FileName in~ (SuspiciousChildren)
| project
    TimeGenerated,
    DeviceName,
    AccountName,
    InitiatingProcessFileName,
    InitiatingProcessCommandLine,
    FileName,
    ProcessCommandLine,
    SHA256,
    InitiatingProcessId,
    ProcessId
| order by TimeGenerated desc;
// Secondary hunt: X_T file downloads or email attachments
// Requires Defender for Office 365 or network file monitoring
DeviceFileEvents
| where TimeGenerated > ago(30d)
| where FileName endswith ".x_t"
| where FolderPath has_any ("Downloads", "Temp", "AppData", "INetCache")
| project
    TimeGenerated,
    DeviceName,
    FileName,
    FolderPath,
    SHA256,
    ActionType,
    InitiatingProcessFileName,
    InitiatingProcessCommandLine
| order by TimeGenerated desc

Velociraptor VQL Hunt

VQL — Velociraptor
-- Hunt for Femap child processes and recent X_T file access
-- Artifact: CVE-2026-64629 exploitation indicators
SELECT
    Pid,
    Ppid,
    Name,
    CommandLine,
    Exe,
    Username,
    CreateTime
FROM pslist()
WHERE Name =~ '(?i)femap'
   OR (
       Ppid IN (
           SELECT Pid FROM pslist() WHERE Name =~ '(?i)femap'
       )
       AND Name =~ '(?i)(cmd|powershell|pwsh|wscript|cscript|mshta|rundll32|regsvr32|certutil|bitsadmin)'
   )
ORDER BY CreateTime DESC
VQL — Velociraptor
-- Hunt for recently created or modified X_T files in common delivery locations
SELECT
    FullPath,
    Size,
    Mtime,
    Atime
FROM glob(
    globs=[
        'C:/Users/*/Downloads/**/*.x_t',
        'C:/Users/*/AppData/Local/Temp/**/*.x_t',
        'C:/Users/*/Desktop/**/*.x_t'
    ]
)
WHERE Mtime > now() - 30 * 24 * 3600
ORDER BY Mtime DESC

Remediation Script

PowerShell
#Requires -RunAsAdministrator
# CVE-2026-64629 — Siemens Simcenter Femap Out-of-Bounds Read
# Verify installed version and flag if patching is required
# Security Arsenal — 2026-01-16

$FixedVersion = [version]"2606.0002"
$Vulnerable = $false

Write-Host "=== CVE-2026-64629 Femap Vulnerability Check ===" -ForegroundColor Cyan

# Check installed programs for Simcenter Femap
$femapInstalls = @()
$registryPaths = @(
    "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
    "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*",
    "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*"
)

foreach ($path in $registryPaths) {
    $found = Get-ItemProperty -Path $path -ErrorAction SilentlyContinue |
        Where-Object { $_.DisplayName -match "Femap|Simcenter Femap" }
    if ($found) { $femapInstalls += $found }
}

if ($femapInstalls.Count -eq 0) {
    Write-Host "[INFO] Simcenter Femap not found in registry uninstall keys." -ForegroundColor Yellow

    # Fallback: Check common installation directories
    $commonPaths = @(
        "C:\Program Files\Siemens\Femap*",
        "C:\Program Files (x86)\Siemens\Femap*"
    )
    foreach ($cp in $commonPaths) {
        $dirs = Get-Item -Path $cp -ErrorAction SilentlyContinue
        if ($dirs) {
            Write-Host "[FOUND] Femap installation directory: $($dirs.FullName)" -ForegroundColor Yellow
        }
    }
}
else {
    foreach ($install in $femapInstalls) {
        $installedVersion = $install.DisplayVersion
        Write-Host "`n[FOUND] $($install.DisplayName)" -ForegroundColor Green
        Write-Host "  Version: $installedVersion"
        Write-Host "  Location: $($install.InstallLocation)"

        # Parse version — Femap versions may use various formats
        $versionString = $installedVersion -replace '[^0-9.]', ''
        try {
            $parsedVersion = [version]$versionString
            if ($parsedVersion -lt $FixedVersion) {
                Write-Host "  [VULNERABLE] Version $installedVersion is below $FixedVersion" -ForegroundColor Red
                Write-Host "  ACTION REQUIRED: Update to Simcenter Femap 2606.0002 or later" -ForegroundColor Red
                $Vulnerable = $true
            }
            else {
                Write-Host "  [PATCHED] Version $installedVersion meets or exceeds $FixedVersion" -ForegroundColor Green
            }
        }
        catch {
            Write-Host "  [WARNING] Could not parse version string '$installedVersion'. Manual verification required." -ForegroundColor Yellow
        }
    }
}

# Check for femap.exe file version as secondary verification
$femapExePaths = @(
    "C:\Program Files\Siemens\Femap*\femap.exe",
    "C:\Program Files (x86)\Siemens\Femap*\femap.exe"
)
foreach ($exePath in $femapExePaths) {
    $exe = Get-Item -Path $exePath -ErrorAction SilentlyContinue
    if ($exe) {
        $fileVersion = $exe.VersionInfo.ProductVersion
        Write-Host "`n[BINARY] $($exe.FullName)" -ForegroundColor Cyan
        Write-Host "  Product Version: $fileVersion"
        try {
            $parsedFileVersion = [version]($fileVersion -replace '[^0-9.]', '')
            if ($parsedFileVersion -lt $FixedVersion) {
                Write-Host "  [VULNERABLE] Binary version below fixed version" -ForegroundColor Red
                $Vulnerable = $true
            }
            else {
                Write-Host "  [PATCHED] Binary version is current" -ForegroundColor Green
            }
        }
        catch {
            Write-Host "  [WARNING] Could not parse binary version" -ForegroundColor Yellow
        }
    }
}

# Summary
Write-Host "`n=== SUMMARY ===" -ForegroundColor Cyan
if ($Vulnerable) {
    Write-Host "STATUS: VULNERABLE — Immediate patching required" -ForegroundColor Red
    Write-Host "Download the latest version from Siemens Support Center" -ForegroundColor Red
    Write-Host "Advisory: https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-10" -ForegroundColor Red
    exit 1
}
else {
    Write-Host "STATUS: No vulnerable Femap installations detected" -ForegroundColor Green
    exit 0
}

Remediation

Primary Action: Patch Immediately

Siemens has released Simcenter Femap version 2606.0002, which remediates CVE-2026-64629. All organizations running Simcenter Femap should update to this version or later as soon as operationally feasible.

  • Vendor Advisory: CISA ICS Advisory ICSA-26-321-10
  • Vendor Security Portal: Refer to the Siemens ProductCERT Security Advisory for the official patch download and release notes (accessible via the Siemens Support Center)
  • CISA KEV Status: Not currently listed — no CISA-mandated remediation deadline applies at this time, but organizations should not wait for a KEV listing to act

Compensating Controls (If Immediate Patching Is Not Possible)

  1. Restrict X_T file ingestion: Implement policies requiring all X_T files from external sources to be validated or converted through a controlled intermediary before being opened in Femap. Use application whitelisting to prevent Femap from opening files outside designated trusted directories.

  2. Email and web gateway filtering: Configure email gateways and web proxies to flag or quarantine .x_t file attachments from external senders. Treat engineering file formats with the same scrutiny as Office documents and PDFs.

  3. Application isolation: Where feasible, run Simcenter Femap in a sandboxed or virtualized environment when opening files from untrusted sources. This limits the blast radius of successful exploitation.

  4. Endpoint detection tuning: Deploy the Sigma rules and KQL queries provided above. Ensure your EDR platform monitors Femap process trees for anomalous child process creation.

  5. Network segmentation: Engineering workstations running CAD/CAE software should reside on segmented VLANs with restricted outbound access. A compromised Femap instance should not have unrestricted lateral movement paths to OT or production networks.

  6. User awareness: Brief engineering and design teams on the risk of opening unsolicited X_T files. Unlike typical phishing awareness training focused on Office macros, this conversation should specifically address the supply-chain risk inherent in CAD file exchange workflows.

Broader Strategic Recommendations

  • Inventory engineering file types: Most organizations have robust controls around executables and Office macros but treat CAD/CAE file formats as benign. Extend your file-handling security policies to cover Parasolid X_T, STEP, IGES, JT, and other engineering formats that are routinely parsed by complex applications with large attack surfaces.
  • Include CAE tools in vulnerability management: Engineering applications like Femap are frequently excluded from standard patch cycles because they are "specialized tools." This creates a persistent gap. Ensure your vulnerability management program covers engineering software with the same rigor as browsers and office suites.
  • Monitor Siemens ProductCERT: Subscribe to Siemens ProductCERT advisories for ongoing security notifications affecting Simcenter and other Siemens product lines deployed in your environment.

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.