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

QNAP Systems Inc.

QTS

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 qts, 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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2024-48866 6 Dec 2024 5.1.x < 5.1.9.2954 build 20241120; 5.2.x < 5.2.2.2950 build 20241114; h5.1.x < h5.1.9.2954 build 20241120; h5.2.x < h5.2.2.2952 build 20241116 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-48865 6 Dec 2024 5.1.x < 5.1.9.2954 build 20241120; 5.2.x < 5.2.2.2950 build 20241114; h5.1.x < h5.1.9.2954 build 20241120; h5.2.x < h5.2.2.2952 build 20241116 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-48859 6 Dec 2024 5.1.x < 5.1.9.2954 build 20241120; 5.2.x < 5.2.2.2950 build 20241114; h5.1.x < h5.1.9.2954 build 20241120; h5.2.x < h5.2.2.2952 build 20241116 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-53691 6 Dec 2024 5.1.x < 5.1.8.2823 build 20240712; 5.2.x < 5.2.0.2802 build 20240620; h5.1.x < h5.1.8.2823 build 20240712; h5.2.x < h5.2.0.2802 build 20240620 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37041 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37042 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37043 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37044 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37045 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37046 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37047 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37048 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37049 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37050 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50396 22 Nov 2024 ? < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50397 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50398 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50399 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50400 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50401 22 Nov 2024 5.2.x < 5.2.1.2930 build 20241025; h5.2.x < h5.2.1.2929 build 20241025 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-38641 6 Sep 2024 5.1.x < 5.1.8.2823 build 20240712; h5.1.x < h5.1.8.2823 build 20240712 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-32763 6 Sep 2024 5.1.x < 5.1.8.2823 build 20240712; h5.1.x < h5.1.8.2823 build 20240712 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21906 6 Sep 2024 5.1.x < 5.1.8.2823 build 20240712; h5.1.x < h5.1.8.2823 build 20240712 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34979 6 Sep 2024 4.5.x < 4.5.4.2790 build 20240605; h4.5.x < h4.5.4.2790 build 20240606 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34974 6 Sep 2024 4.5.x < 4.5.4.2790 build 20240605; h4.5.x < h4.5.4.2626 build 20231225 c5.x.x; 5.1.0; 2.2.0 Update reference ↗
CVE-2024-32771 6 Sep 2024 5.1.x < 5.2.0.2782 build 20240601; h5.1.x < h5.2.0.2782 build 20240601 5.0.x; 4.5.x; h5.0.x; h4.5.x; c5.0.x Update reference ↗
CVE-2023-39298 6 Sep 2024 5.1.x < 5.2.0.2737 build 20240417; h5.1.x < h5.2.0.2782 build 20240601 5.0.x; 4.5.x; h5.0.x; h4.5.x; c5.0.x < h5.2.0.2782 build 20240601 Update reference ↗
CVE-2023-39300 6 Sep 2024 4.3.6 < 4.3.6.2805 build 20240619; 4.3.4 < 4.3.4.2814 build 20240618; 4.3.3 < 4.3.3.2784 build 20240619; 4.2.6 < 4.2.6 build 20240618 5.x; 4.5.x; h5.x; h4.5.x; c5.x Update reference ↗
CVE-2024-21904 6 Sep 2024 5.1.x < 5.1.7.2770 build 20240520; h5.1.x < h5.1.7.2770 build 20240520 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21903 6 Sep 2024 5.1.x < 5.1.6.2722 build 20240402; h5.1.x < h5.1.6.2734 build 20240414 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21898 6 Sep 2024 5.1.x < 5.1.6.2722 build 20240402; h5.1.x < h5.1.6.2734 build 20240414 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21897 6 Sep 2024 5.1.x < 5.1.6.2722 build 20240402; h5.1.x < h5.1.6.2734 build 20240414 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51368 6 Sep 2024 5.1.x < 5.1.6.2722 build 20240402; h5.1.x < h5.1.6.2734 build 20240414 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51367 6 Sep 2024 5.1.x < 5.1.6.2722 build 20240402 h5.1.x < h5.1.6.2734 build 20240414 Update reference ↗
CVE-2023-51366 6 Sep 2024 5.1.x < 5.1.6.2722 build 20240402 h5.1.x < h5.1.6.2734 build 20240414 Update reference ↗
CVE-2023-50366 6 Sep 2024 5.1.x < 5.1.6.2722 build 20240402; h5.1.x < h5.1.6.2734 build 20240414 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-32765 9 Aug 2024 5.1.x < 5.1.8.2823 build 20240712; h5.1.x < h5.1.8.2823 build 20240712 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-27130 21 May 2024 5.1.x < 5.1.7.2770 build 20240520; h5.1.x < h5.1.7.2770 build 20240520 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-27129 21 May 2024 5.1.x < 5.1.7.2770 build 20240520; h5.1.x < h5.1.7.2770 build 20240520 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-27128 21 May 2024 5.1.x < 5.1.7.2770 build 20240520; h5.1.x < h5.1.7.2770 build 20240520 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-27127 21 May 2024 5.1.x < 5.1.7.2770 build 20240520; h5.1.x < h5.1.7.2770 build 20240520 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21902 21 May 2024 5.1.x < 5.1.7.2770 build 20240520; h5.1.x < h5.1.7.2770 build 20240520 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50361 26 Apr 2024 5.1.x < 5.1.6.2722 build 20240402; h5.1.x < h5.1.6.2734 build 20240414 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50362 26 Apr 2024 5.1.x < 5.1.6.2722 build 20240402; h5.1.x < h5.1.6.2734 build 20240414 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50363 26 Apr 2024 5.1.x < 5.1.6.2722 build 20240402; h5.1.x < h5.1.6.2734 build 20240414 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50364 26 Apr 2024 5.1.x < 5.1.6.2722 build 20240402; h5.1.x < h5.1.6.2734 build 20240414 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51364 26 Apr 2024 5.1.x < 5.1.4.2596 build 20231128; 4.5.x < 4.5.4.2627 build 20231225; h5.1.x < h5.1.3.2578 build 20231110; h4.5.x < h4.5.4.2626 build 20231225; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51365 26 Apr 2024 5.1.x < 5.1.4.2596 build 20231128; 4.5.x < 4.5.4.2627 build 20231225; h5.1.x < h5.1.3.2578 build 20231110; h4.5.x < h4.5.4.2626 build 20231225 c5.x < c5.1.5.2651 Update reference ↗
CVE-2024-21905 26 Apr 2024 5.1.x < 5.1.3.2578 build 20231110; h5.1.x < h5.1.3.2578 build 20231110; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-27124 26 Apr 2024 5.1.x < 5.1.3.2578 build 20231110; 4.5.x < 4.5.4.2627 build 20231225; h5.1.x < h5.1.3.2578 build 20231110; h4.5.x < h4.5.4.2626 build 20231225; c5.x.x < c5.1.5.2651 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.