CISA Details Simcenter Femap X_T Parsing Fix in 2606.0002

P1 — VALIDATE AND UPDATEHigh · 7.8 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Update Simcenter Femap to 2606.0002 or later and review the provenance of X_T models supplied to engineering users.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Femap builds, engineering workstation owners, model exchange sources and plugins or automation that import X_T files. The attack depends on a user processing a crafted file. Evaluate file-transfer and review controls; a high score alone does not establish exploitation. Deploy the supported 2606.0002 or later update. Restrict untrusted model intake until the fixed build is installed. Test representative model import, analysis and export operations with approved files. Retain installed-build evidence, installer provenance, regression results and change approval.

Open the authoritative advisory

Last verified: 2026-11-17 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeSiemens Simcenter Femap
AdvisoryICSA-26-321-10
CVECVE-2026-64629
Authoritative release date2026-11-17T12:00:00Z — CISA release timestamp in the advisory page.
Authority revision dateNo separate material revision is confirmed for this CISA release.
Affected versionsSimcenter Femap versions before 2606.0002.
Fixed versionSimcenter Femap 2606.0002 or later
CVSS base score7.8 (CVSS v3.1)
CVSS severityHigh
Exploitation statusThe cited CISA ICS advisory does not confirm exploitation of these products in the wild.; no exploitation claim is inferred.

What Changed

CISA describes an out-of-bounds read while importing a crafted X_T file that can crash Femap or execute code in the application process.

What To Validate Now

  1. Inventory. Record Femap builds, engineering workstation owners, model exchange sources and plugins or automation that import X_T files.
  2. Establish applicability. The attack depends on a user processing a crafted file. Evaluate file-transfer and review controls; a high score alone does not establish exploitation.
  3. Remediate. Deploy the supported 2606.0002 or later update. Restrict untrusted model intake until the fixed build is installed.
  4. Validate. Test representative model import, analysis and export operations with approved files. Retain installed-build evidence, installer provenance, regression results and change approval.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Validate engineering compatibility and recovery before changing production workstations. Do not test suspected malicious models in the operational environment.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.