dbcve.org
Simcenter FemapApplication · Siemens

CVE-2026-23720

HIGH · 7.3 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 2512.0000 or later.
See remediation →
73/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in Simcenter Femap (All versions < V2512), Simcenter Nastran (All versions < V2512). The affected applications contains an out of bounds read vulnerability while parsing specially crafted NDB files. This could allow an attacker to execute code in the context of the current process.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Out-of-bounds read vulnerability in Simcenter Femap and Nastran when parsing specially crafted NDB files. This memory access violation can be triggered by opening a malicious NDB file, potentially allowing arbitrary code execution in the context of the current user process.

MitigationUpgrade to Simcenter V2512 or later versions. Until upgrade is possible, implement controls to restrict opening of NDB files from untrusted sources and consider running applications with reduced privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Simcenter FemapApplication
Affected:< 2512.0000
Simcenter NastranApplication
Affected:< 2512.0000

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Simcenter product
    Check for Siemens Simcenter Femap or Nastran installation via Add/Remove Programs, program directory, or by launching the applications to confirm presence on the system
    Affected if Either Femap or Nastran or both products are installed on the system
  2. Determine Simcenter Femap version
    Open Femap, then go to Help > About Femap, or right-click the femap.exe file in the installation directory and select Properties > Details to view the version number
    Affected if The displayed version is below 2512.0000 (for example, 2510.0000, 2506.0000, etc.)
  3. Determine Simcenter Nastran version
    Open Nastran, then look for the version information in the application menu or Help > About, or check the nastran.exe file Properties > Details in the installation directory
    Affected if The displayed version is below 2512.0000 (for example, 2510.0000, 2506.0000, etc.)
  4. Verify NDB file handling capability
    Attempt to open or import an NDB file within the installed Femap or Nastran application to confirm the application can process this file type
    Affected if The application successfully opens or imports NDB files, indicating the vulnerable parsing code path is accessible

A system is affected if either Simcenter Femap or Nastran with a version below 2512.0000 is installed and the application can open or import NDB files, which would trigger the vulnerable parsing code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2512.0000 or later
Fixed in 2512.0000
Interim mitigation

Upgrade to Simcenter V2512 or later versions. Until upgrade is possible, implement controls to restrict opening of NDB files from untrusted sources and consider running applications with reduced privileges.

Recommended fix High confidence

V2512 (2512.0000)

  1. 1. Identify the current installed version of Simcenter Femap or Simcenter Nastran via the application's Help > About menu
  2. 2. Navigate to the Siemens Support portal or authorized distribution channel to obtain version V2512.0000 or later
  3. 3. Download the installer for the appropriate product (Femap or Nastran) matching your license type
  4. 4. Before upgrading, back up any existing project files, custom templates, and configuration settings
  5. 5. Run the installer and follow the on-screen prompts to complete the upgrade
  6. 6. After installation, verify the version number displays as 2512.0000 or higher in the application's About dialog
  7. 7. Test that NDB file parsing functionality works normally with the updated version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Simcenter Femap Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23720 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23720 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data