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-32766 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
CVE-2024-21900 8 Mar 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-21899 8 Mar 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
CVE-2023-34980 8 Mar 2024 4.5.x < 4.5.4.2627 build 20231225; h4.5.x < h4.5.4.2626 build 20231225 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50358 13 Feb 2024 5.x < 5.1.5.2645 build 20240116; 4.5.x, 4.4.x < 4.5.4.2627 build 20231225; 4.3.6, 4.3.5 < 4.3.6.2665 build 20240131; 4.3.4 < 4.3.4.2675 build 20240131; 4.3.x < 4.3.3.2644 build 20240131; 4.2.x < 4.2.6 build 20240131; h5.x < h5.1.5.2647 build 20240118; h4.x < h4.5.4.2626 build 20231225 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47218 13 Feb 2024 5.1.x < 5.1.5.2645 build 20240116; h5.1.x < h5.1.5.2647 build 20240118; c5.x < c5.1.5.2651 4.x; h4.x Update reference ↗
CVE-2023-50359 2 Feb 2024 5.1.x < 5.1.5.2645 build 20240116; h5.1.x < h5.1.5.2647 build 20240118 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47568 2 Feb 2024 5.1.x < 5.1.5.2645 build 20240116; 4.5.x < 4.5.4.2627 build 20231225; h5.1.x < h5.1.5.2647 build 20240118; 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-47567 2 Feb 2024 5.1.x < 5.1.5.2645 build 20240116; 4.5.x < 4.5.4.2627 build 20231225; h5.1.x < h5.1.5.2647 build 20240118; 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-47566 2 Feb 2024 5.1.x < 5.1.5.2645 build 20240116; h5.1.x < h5.1.5.2647 build 20240118; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45037 2 Feb 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-2023-45036 2 Feb 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-2023-45035 2 Feb 2024 5.1.x < 5.1.4.2596 build 20231128; h5.1.x < h5.1.4.2596 build 20231128; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45028 2 Feb 2024 5.1.x < 5.1.5.2645 build 20240116; h5.1.x < h5.1.5.2647 build 20240118; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45027 2 Feb 2024 5.1.x < 5.1.5.2645 build 20240116; h5.1.x < h5.1.5.2647 build 20240118; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45026 2 Feb 2024 5.1.x < 5.1.5.2645 build 20240116; h5.1.x < h5.1.5.2647 build 20240118; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45025 2 Feb 2024 5.1.x < 5.1.4.2596 build 20231128; 4.5.x < 4.5.4.2627 build 20231225; h5.1.x < h5.1.4.2596 build 20231128; 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-41292 2 Feb 2024 5.1.x < 5.1.4.2596 build 20231128; h5.1.x < h5.1.4.2596 build 20231128; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41283 2 Feb 2024 5.1.x < 5.1.4.2596 build 20231128; h5.1.x < h5.1.4.2596 build 20231128; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41282 2 Feb 2024 5.1.x < 5.1.4.2596 build 20231128; h5.1.x < h5.1.4.2596 build 20231128; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41281 2 Feb 2024 5.1.x < 5.1.4.2596 build 20231128; h5.1.x < h5.1.4.2596 build 20231128; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41280 2 Feb 2024 5.1.x < 5.1.2.2533 build 20230926; h5.1.x < h5.1.2.2534 build 20230927; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41279 2 Feb 2024 5.1.x < 5.1.2.2533 build 20230926; h5.1.x < h5.1.2.2534 build 20230927; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41278 2 Feb 2024 5.1.x < 5.1.2.2533 build 20230926; h5.1.x < h5.1.2.2534 build 20230927; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41277 2 Feb 2024 5.1.x < 5.1.2.2533 build 20230926; h5.1.x < h5.1.2.2534 build 20230927; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41276 2 Feb 2024 5.1.x < 5.1.2.2533 build 20230926; h5.1.x < h5.1.2.2534 build 20230927; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41275 2 Feb 2024 5.1.x < 5.1.2.2533 build 20230926; h5.1.x < h5.1.2.2534 build 20230927; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41274 2 Feb 2024 5.1.x < 5.1.2.2533 build 20230926; h5.1.x < h5.1.2.2534 build 20230927; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41273 2 Feb 2024 5.1.x < 5.1.2.2533 build 20230926; h5.1.x < h5.1.2.2534 build 20230927; c5.x.x < c5.1.5.2651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-39303 2 Feb 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-2023-39297 2 Feb 2024 5.1.x < 5.1.4.2596 build 20231128; 4.5.x < 4.5.4.2627 build 20231225; h5.1.x < h5.1.4.2596 build 20231128; 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-39302 2 Feb 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-2023-39294 5 Jan 2024 5.1.x < 5.1.3.2578 build 20231110; h5.1.x < h5.1.3.2578 build 20231110 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-39296 5 Jan 2024 5.1.x < 5.1.3.2578 build 20231110; h5.1.x < h5.1.3.2578 build 20231110 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45040 5 Jan 2024 5.1.x < 5.1.4.2596 build 20231128; h5.1.x < h5.1.4.2596 build 20231128 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45039 5 Jan 2024 5.1.x < 5.1.4.2596 build 20231128; h5.1.x < h5.1.4.2596 build 20231128 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-32968 8 Dec 2023 5.0.x < 5.0.1.2514 build 20230906; 5.1.x < 5.1.2.2533 build 20230926; h5.0.x < h5.0.1.2515 build 20230907; h5.1.x < h5.1.2.2534 build 20230927 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-23372 8 Dec 2023 5.0.x < 5.0.1.2425 build 20230609; 5.1.x < 5.1.0.2444 build 20230629; 4.5.x < 4.5.4.2467 build 20230718; h5.1.x < h5.1.0.2424 build 20230609; h5.0.x < h5.0.1.2515 build 20230907; h4.5.x < h4.5.4.2476 build 20230728 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-32975 8 Dec 2023 5.0.x < 5.0.1.2514 build 20230906; 5.1.x < 5.1.2.2533 build 20230926; h5.0.x < h5.0.1.2515 build 20230907; h5.1.x < h5.1.2.2534 build 20230927 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-23367 10 Nov 2023 5.0.x < 5.0.1.2376 build 20230421; h5.0.x < h5.0.1.2376 build 20230421; c5.x.x < c5.1.0.2498 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-39301 3 Nov 2023 5.0.x < 5.0.1.2514 build 20230906; 5.1.x < 5.1.1.2491 build 20230815; h5.0.x < h5.0.1.2515 build 20230907; h5.1.x < h5.1.1.2488 build 20230812; c5.x.x < c5.1.0.2498 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-23368 3 Nov 2023 5.0.x < 5.0.1.2376 build 20230421; 4.5.x < 4.5.4.2374 build 20230416; h5.0.x < h5.0.1.2376 build 20230421; h4.5.x < h4.5.4.2374 build 20230417; c5.x.x < c5.0.1.2374 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-32974 13 Oct 2023 5.1.x < 5.1.0.2444 build 20230629; h5.1.x < h5.1.0.2424 build 20230609; c5.x < c5.1.0.2498 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-32973 13 Oct 2023 5.0.x < 5.0.1.2425 build 20230609; 5.1.x < 5.1.0.2444 build 20230629; 4.5.x < 4.5.4.2467 build 20230718; h5.0.x < h5.0.1.2515 build 20230907; h5.1.x < h5.1.0.2424 build 20230609; h4.5.x < h4.5.4.2476 build 20230728; c5.x < c5.1.0.2498 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-32972 6 Oct 2023 5.0.x < 5.0.1.2425 build 20230609; 5.1.x < 5.1.0.2444 build 20230629; 4.5.x < 4.5.4.2467 build 20230718; h5.0.x < h5.0.1.2515 build 20230907; h5.1.x < h5.1.0.2424 build 20230609; h4.5.x < h4.5.4.2476 build 20230728; c5.0.x < c5.1.0.2498 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-32971 6 Oct 2023 5.0.x < 5.0.1.2425 build 20230609; 5.1.x < 5.1.0.2444 build 20230629; 4.5.x < 4.5.4.2467 build 20230718; h5.0.x < h5.0.1.2515 build 20230907; h5.1.x < h5.1.0.2424 build 20230609; h4.5.x < h4.5.4.2476 build 20230728; c5.0.x < c5.1.0.2498 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-23363 22 Sep 2023 4.3.* < 4.3.6.2441 build 20230621; 4.3.* < 4.3.3.2420 build 20230621; 4.2.* < 4.2.6 build 20230621; 4.3.* < 4.3.4.2451 build 20230621 4.5.*; 5.*.* Update reference ↗
CVE-2023-23362 22 Sep 2023 5.0.* < 5.0.1.2376 build 20230421; 4.5.* < 4.5.4.2374 build 20230416; h5.0.* < h5.0.1.2376 build 20230421; h4.5.* < h4.5.4.2374 build 20230417; c5.0.1 < c5.0.1.2374 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34973 24 Aug 2023 5.0.* < 5.0.1.2425 build 20230609; 5.1.* < 5.1.0.2444 build 20230629; h5.1.* < h5.1.0.2424 build 20230609 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34972 24 Aug 2023 5.0.* < 5.0.1.2425 build 20230609; 5.1.* < 5.1.0.2444 build 20230629; h5.1.* < h5.1.0.2424 build 20230609 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.