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

Siemens

RUGGEDCOM ROX MX5000

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-2025-40949 12 May 2026 < V2.17.1 Update to V2.17.1 or later version Update reference ↗
CVE-2025-40948 12 May 2026 < V2.17.1 Update to V2.17.1 or later version Update reference ↗
CVE-2025-40947 12 May 2026 < V2.17.1 Update to V2.17.1 or later version Update reference ↗
CVE-2024-56840 9 Dec 2025 < V2.17.0 Update to V2.17.0 or later version Update reference ↗
CVE-2024-56839 9 Dec 2025 < V2.17.0 Update to V2.17.0 or later version Update reference ↗
CVE-2024-56838 9 Dec 2025 < V2.17.0 Update to V2.17.0 or later version Update reference ↗
CVE-2024-56837 9 Dec 2025 < V2.17.0 Update to V2.17.0 or later version Update reference ↗
CVE-2024-56836 9 Dec 2025 < V2.17.0 Update to V2.17.0 or later version Update reference ↗
CVE-2024-56835 9 Dec 2025 < V2.17.0 Update to V2.17.0 or later version Update reference ↗
CVE-2025-40761 12 Aug 2025 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-33023 12 Aug 2025 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-40591 10 Jun 2025 < V2.16.5 Update to V2.16.5 or later version Update reference ↗
CVE-2025-33025 13 May 2025 < V2.16.5 Update to V2.16.5 or later version Update reference ↗
CVE-2025-33024 13 May 2025 < V2.16.5 Update to V2.16.5 or later version Update reference ↗
CVE-2025-32469 13 May 2025 < V2.16.5 Update to V2.16.5 or later version Update reference ↗
CVE-2020-28398 10 Dec 2024 < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36755 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36754 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36753 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36752 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36751 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36750 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36749 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36748 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36390 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36389 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2023-36386 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2022-29562 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2022-29561 11 Jul 2023 All versions < V2.16.0 Update to V2.16.0 or later version Update reference ↗
CVE-2022-29560 12 Jul 2022 All versions < 2.15.1 Update to V2.15.1 or later version Update reference ↗
CVE-2021-41546 12 Oct 2021 All versions < V2.14.1 Update to V2.14.1 or later version Update reference ↗
CVE-2021-37175 14 Sep 2021 All versions < V2.14.1 Update to V2.14.1 or later version Update reference ↗
CVE-2021-37174 14 Sep 2021 All versions < V2.14.1 Update to V2.14.1 or later version Update reference ↗
CVE-2021-37173 14 Sep 2021 All versions < V2.14.1 Update to V2.14.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.