dbcve.org
Simcenter FemapApplication · Siemens

CVE-2026-23718

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

An out-of-bounds read vulnerability exists in Simcenter Femap and Simcenter Nastran when parsing specially crafted NDB files. The vulnerability allows reading memory beyond allocated buffers, which can be weaponized to achieve arbitrary code execution in the context of the current process.

MitigationUpdate both Simcenter Femap and Simcenter Nastran to version V2512 or later to remediate this vulnerability. Until patched, avoid opening NDB files from untrusted sources.

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. Check Simcenter Femap installation and version
    Locate the Simcenter Femap installation directory and identify the installed version number. This can typically be done through the program's Help > About menu, or by checking the executable file properties in the installation folder.
    Affected if The installed version is present and is less than 2512.0000
  2. Check Simcenter Nastran installation and version
    Locate the Simcenter Nastran installation directory and identify the installed version number. This is usually accessible through the application's Help > About dialog, or by viewing the properties of the main executable file.
    Affected if The installed version is present and is less than 2512.0000
  3. Verify NDB file parsing capability
    Confirm that the installed software includes the capability to open or import NDB files, which is the file format associated with the vulnerability.
    Affected if The software can process NDB files and the version is below 2512.0000

If either Simcenter Femap or Simcenter Nastran is installed with a version lower than 2512.0000 and has the ability to parse NDB files, the environment is affected by this vulnerability.

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

Update both Simcenter Femap and Simcenter Nastran to version V2512 or later to remediate this vulnerability. Until patched, avoid opening NDB files from untrusted sources.

Recommended fix High confidence

Simcenter Femap V2512.0000 or later / Simcenter Nastran V2512.0000 or later

  1. 1. Identify the current installed version of Simcenter Femap or Simcenter Nastran by opening the application and navigating to Help > About, or checking the installation directory for version information.
  2. 2. Navigate to the Siemens Support portal or cert-portal.siemens.com to download Simcenter Femap version 2512.0000 or later.
  3. 3. Alternatively, navigate to the Siemens Support portal or cert-portal.siemens.com to download Simcenter Nastran version 2512.0000 or later.
  4. 4. Ensure you have a complete backup of all critical project files, NDB files, and configuration data before proceeding with the upgrade.
  5. 5. Uninstall the current version of the affected product, or use the update/installation mechanism provided by Siemens to apply the upgrade.
  6. 6. Install version 2512.0000 or later of the chosen product (Femap or Nastran).
  7. 7. After installation, verify the version by opening the application and checking Help > About to confirm the installed version is 2512.0000 or higher.
  8. 8. Test critical workflows with your NDB files to ensure normal operation after the upgrade.
Caveat Review the Siemens release notes for V2512 to check for any workflow changes or migration requirements; standard upgrade risks apply

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

Fix this in Simcenter Femap Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23718 — 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-23718 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