Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY40 SECURITY RECORDS

Siemens

Simcenter Femap

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-59701 11 Aug 2026 < V2606.0001 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-59700 11 Aug 2026 < V2606.0001 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-59086 11 Aug 2026 < V2606 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-12659 12 May 2026 Simcenter Femap: < V2512.0003 Simcenter Femap: V2512.0003 Update reference ↗
CVE-2026-23720 10 Feb 2026 < V2512 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-23719 10 Feb 2026 < V2512 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-23718 10 Feb 2026 < V2512 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-23717 10 Feb 2026 < V2512 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-23716 10 Feb 2026 < V2512 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-23715 10 Feb 2026 < V2512 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-40829 12 Dec 2025 Simcenter Femap: < V2512 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-33654 9 Jul 2024 < V2406 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-33653 9 Jul 2024 < V2406 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-32056 9 Jul 2024 < V2406 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-33577 14 May 2024 < V2406 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-32066 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32065 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32064 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32063 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32062 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32061 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32060 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32059 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32058 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32057 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-32055 14 May 2024 < V2406 Update to V27.1.215 or later version Update reference ↗
CVE-2024-27907 12 Mar 2024 < V2306.0000 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-24925 13 Feb 2024 < V2306.0000 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-24924 13 Feb 2024 < V2306.0000 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-24923 13 Feb 2024 < V2401.0000; < V2306.0001 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-24922 13 Feb 2024 < V2401.0000 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-24921 13 Feb 2024 < V2401.0000 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-24920 13 Feb 2024 < V2401.0000 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-34748 12 Jul 2022 All versions < V2022.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-27653 10 May 2022 All versions < V2022.2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-28663 12 Apr 2022 All versions < V2022.1.2 Update to V2022.1.2 or later version Update reference ↗
CVE-2022-28662 12 Apr 2022 All versions < V2022.1.2 Update to V2022.1.2 or later version Update reference ↗
CVE-2022-28661 12 Apr 2022 All versions < V2022.1.2 Update to V2022.1.2 or later version Update reference ↗
CVE-2021-46699 22 Feb 2022 All versions < V2022.1.1 Update to V2022.1.1 or later version Update reference ↗
CVE-2021-46162 22 Feb 2022 All versions < V2022.1.1 Update to V2022.1.1 or later version Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.