ics-otregulatorNewsThe Broadside1 min read

Siemens patches Femap X_T file parsing flaw

The fourth Femap file-parsing advisory CISA has republished this year, landing on the same 7.8 and the same update-to-latest fix.


TL;DR

CISA republished Siemens' advisory for an out-of-bounds read (CVE-2026-64629, CWE-125) in Simcenter Femap's X_T parser. A crafted X_T file triggers arbitrary code execution in the current process; versions before V2606.0002 are affected, and that release is the fix. Critical manufacturing deployments worldwide are in scope. It's the fourth Femap file-parsing advisory CISA has republished this year, again a 7.8 and again a version bump.

CVE-2026-64629 is an out-of-bounds read (CWE-125) reached while Simcenter Femap parses X_T files. Siemens fixed it in V2606.0002, and CISA republished ProductCERT's SSA-105852 as ICSA-26-321-10. The 7.8 base score sits on a local vector with low attack complexity and no privileges required, gated by user interaction: an attacker who gets an engineer to open a crafted X_T file can run code in the context of the current process.

That file-open surface keeps yielding the same result, and it isn't the first time this year. This is the fourth Femap file-parsing advisory CISA has republished in 2026, after August's BMP parsing bugs (CVE-2026-59700, CVE-2026-59701), May's IPT parser flaw, and February's NDB and XDB issues across Femap and Nastran. Every one landed at 7.8 with the same local, user-interaction-gated vector, and every fix was a version bump.

For teams running Femap in critical manufacturing, the path is straightforward: move to V2606.0002 or later. The change control that governs that design tooling stack is the only gate left standing.


Published ·Deep Fathom