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

SAP SE

SAP BusinessObjects Business Intelligence platform

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-0502 12 May 2026 ENTERPRISE 430; 2025; 2027 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-27683 14 Apr 2026 ENTERPRISE 430; 2025; 2027 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24318 14 Apr 2026 ENTERPRISE 430; 2025; 2027 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0508 10 Feb 2026 ENTERPRISE 430; 2025; 2027 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-42896 9 Dec 2025 SAP BusinessObjects Business Intelligence Platform: ENTERPRISE 430, 2025, 2027 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-31332 8 Apr 2025 ENTERPRISE 430 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-0062 11 Mar 2025 ENTERPRISE 430; 2025; ENTERPRISECLIENTTOOLS 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0061 14 Jan 2025 ENTERPRISE 420; 430; 2025 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-2025-0060 14 Jan 2025 ENTERPRISE 420; 430; 2025 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-2024-32732 10 Dec 2024 ENTERPRISE 430; 2025 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-2024-45281 10 Sep 2024 430 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-2024-41731 13 Aug 2024 ENTERPRISE 430; 2025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-28166 13 Aug 2024 ENTERPRISE 430; 2025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42375 13 Aug 2024 ENTERPRISE 430; 2025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41730 13 Aug 2024 ENTERPRISE 430; 440 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-34684 11 Jun 2024 ENTERPRISE 420; 430; 440 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-2024-28165 14 May 2024 430; 440 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-2023-36917 11 Jul 2023 4.20; 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-31406 9 May 2023 420; 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-30741 9 May 2023 420; 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-30740 9 May 2023 420; 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-0020 14 Feb 2023 420; 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-0015 10 Jan 2023 420 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29619 12 Jul 2022 420; 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-27671 12 Apr 2022 420; 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28213 12 Apr 2022 420; 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-22541 12 Apr 2022 420; 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-27667 12 Apr 2022 430 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-42061 14 Dec 2021 < 420 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6251 12 May 2020 < 4.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6221 14 Apr 2020 < 4.1; < 4.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-0289 14 May 2019 < 4.2; < 4.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-2483 13 Nov 2018 = 4.1; = 4.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-2472 9 Oct 2018 4.10; 4.20 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-2471 9 Oct 2018 4.10; 4.20 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-2445 14 Aug 2018 4.1; 4.2 No fixed version is explicitly recorded in the structured CVE data. 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.