LoadMaster

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

Lifecycle evidence status

Official registry publication history is available at loadmaster, but registry activity is not a publisher support boundary.

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-2026-59690	27 Jul 2026	7.0.6 < 7.2.63.3; 7.0.6 < 7.2.54.19; 7.2.60.0 < 7.2.63.3; 7.1.29 < 7.1.35.16	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2026-59689	27 Jul 2026	7.2.36 < 7.2.63.3; 7.2.36 < 7.2.54.19; 7.2.60.0 < 7.2.63.3	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2026-59688	27 Jul 2026	7.2.40.0 < 7.2.63.3; 7.2.40.0 < 7.2.54.19; 7.2.60.0 < 7.2.63.3	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2026-59687	27 Jul 2026	7.0.8 < 7.2.63.3; 7.0.8 < 7.2.54.19; 7.2.60.0 < 7.2.63.3	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2026-59686	27 Jul 2026	All Previous Versions < 7.2.63.3; All Previous Versions < 7.2.54.19; 7.2.60.0 < 7.2.63.3	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2026-4048	20 Apr 2026	V7.1.20.0 < V7.2.63.0; V7.2.49.0 < V7.2.63.0; V7.2.62.0 < V7.2.63.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-2026-3519	20 Apr 2026	V7.2.45.0 < V7.2.63.0; V7.2.49.0 < V7.2.63.0; V7.2.62.0 < V7.2.63.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-2026-3518	20 Apr 2026	V7.2.37.0 < V7.2.63.0; V7.2.49.0 < V7.2.63.0; V7.2.62.0 < V7.2.63.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-2026-3517	20 Apr 2026	7.1.32.0 < V7.2.63.0; 7.2.49.0 < V7.2.63.0; 7.2.62.0 < V7.2.63.0	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2025-13447	13 Jan 2026	7.2.50 < V7.2.62.2; 7.1.32 < V7.2.62.2; 7.2.37 < V7.2.62.2; 7.2.39 < V7.2.62.2; 7.2.50 < V7.2.54.16; 7.1.32 < V7.2.54.16; 7.2.37 < V7.2.54.16; 7.2.39 < V7.2.54.16	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2025-13444	13 Jan 2026	7.2.50 < V7.2.62.2; 7.2.50 < V7.2.54.16; 7.2.39 < V7.1.35.15	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2024-3544	2 May 2024	LoadMaster 7.2.55.0 (GA) < 7.2.59.4; LoadMaster 7.2.49.0 (LTSF) < 7.2.54.10; LoadMaster 7.2.48.11 (LTS) < 7.2.48.12	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2024-3543	2 May 2024	LoadMaster 7.2.55.0 (GA) < 7.2.59.4; LoadMaster 7.2.49.0 (LTSF) < 7.2.54.10; LoadMaster 7.2.48.11 (LTS) < 7.2.48.12	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2024-2449	22 Mar 2024	7.2.55.0 < 7.2.59.3 ( LoadMaster GA); 7.2.49.0 < 7.2.54.9 ( LoadMaster LTSF); 7.2.48.10 < 7.2.48.11 (LoadMaster LTS); 7.1.35.10 < 7.1.35.11 (LoadMaster MT)	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2024-2448	22 Mar 2024	7.2.55.0 < 7.2.59.3 ( LoadMaster GA); 7.2.49.0 < 7.2.54.9 ( LoadMaster LTSF); 7.2.48.10 < 7.2.48.11 (LoadMaster LTS); 7.1.35.10 < 7.1.35.11 (LoadMaster MT)	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record

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.