Business Automation Workflow

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

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2024-54179	3 Mar 2025	24.0.0; 24.0.1; 24.0.0, 24.0.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2024-43188	18 Sep 2024	22.0.2, 23.0.1, 23.0.2, 24.0.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2024-38321	3 Aug 2024	22.0.2, 23.0.1, 23.0.2, 24.0.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2023-50947	4 Feb 2024	22.0.2, 23.0.1, 23.0.2	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2023-32339	27 Jun 2023	19.0.0.1 ≤ 19.0.0.3; 20.0.0.1 ≤ 20.0.0.2; 21.0.1 ≤ 21.0.3.1; 21.0.1 ≤ 22.0.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-2023-24957	6 May 2023	18.0.0.0, 18.0.0.1, 18.0.0.2, 19.0.0.1, 19.0.0.2, 19.0.0.3, 20.0.0.1, 20.0.0.2, 21.0.2, 21.0.3, 22.0.1, 22.0.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-42435	3 Jan 2023	18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1	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-38390	17 Nov 2022	22.0.1; 21.0.1 < 21.0.3.1; 20.0.0.1 < 20.0.0.2; 19.0.0.1 < 19.0.0.3; 18.0.0.0 < 18.0.0.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-2021-39046	18 Mar 2022	18.0.0.0; 18.0.0.1; 18.0.0.2; 19.0.0.1; 19.0.0.2; 19.0.0.3; 20.0.0.1; 20.0.0.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-2021-38900	21 Dec 2021	18.0.0.0; 18.0.0.1; 18.0.0.2; 19.0.0.1; 19.0.0.2; 19.0.0.3; 20.0.0.1; 20.0.0.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-2021-29835	22 Oct 2021	18.0; 19.0; 20.0; 21.0	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-2021-29878	18 Oct 2021	18.0.0.0; 18.0.0.1; 18.0.0.2; 19.0.0.1; 19.0.0.2; 19.0.0.3; 20.0.0.1; 20.0.0.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-2021-29834	29 Sep 2021	18.0.0.0; 18.0.0.1; 18.0.0.2; 19.0.0.1; 19.0.0.2; 19.0.0.3; 20.0.0.1; 20.0.0.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-2021-29775	28 Jun 2021	18.0.0.0; 18.0.0.1; 18.0.0.2; 19.0.0.1; 19.0.0.2; 19.0.0.3; 20.0.0.1; 20.0.0.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-2020-4768	11 Feb 2021	18.0; 19.0; 20.0; 5.2; 5.3	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2020-4900	30 Nov 2020	19.0.0.3	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-2020-4672	16 Nov 2020	20.0.0.1	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-2020-4531	25 Sep 2020	18.0; 19.0; 20.0; 8.0; 8.5; 8.6	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2019-4669	27 Feb 2020	18.0.0.1; 19.0.0.3; 8.6.0.0; 8.5.7.0; 8.6.0.0.CF2018.03; 8.5.7.0.2017.06	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-2019-4426	13 Dec 2019	18.0.0.1; 19.0.0.2; 5.1.1; 5.2.1; 5.2.0; 5.3CD	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2019-4149	5 Sep 2019	18.0.0.0; 18.0.0.2; 8.6.0.0; 8.5.6.0; 8.5.6.0CF2; 8.5.7.0; 8.5.7.0CF2017.06; 8.6.0.0CF2018.03	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2019-4424	20 Aug 2019	18.0.0.0; 18.0.0.1; 18.0.0.2; 19.0.0.1; 19.0.0.2	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2019-4425	20 Aug 2019	18.0.0.0; 18.0.0.1; 18.0.0.2	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2019-4410	1 Jul 2019	18.0.0.0; 18.0.0.1; 18.0.0.2; 19.0.0.1	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-2019-4204	10 May 2019	18.0.0.0; 18.0.0.1; 18.0.0.2; 19.0.0.1	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-2019-4045	8 Apr 2019	18.0.0.0; 18.0.0.1; 18.0.0.2	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2018-2000	8 Apr 2019	18.0.0.0; 18.0.0.1	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-2018-1999	8 Apr 2019	18.0.0.0; 18.0.0.1; 18.0.0.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-2018-1997	8 Apr 2019	18.0.0.0; 18.0.0.1; 18.0.0.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-2018-1885	8 Apr 2019	18.0.0.0; 18.0.0.1; 18.0.0.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-2018-1848	14 Dec 2018	18.0.0.0; 18.0.0.1	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 ↗

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.