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-2025-52862 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52860 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52859 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52858 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52857 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52855 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52854 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52853 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52433 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52432 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 h5.3.x < h5.3.0.3192 build 20250716 Update reference ↗
CVE-2025-52429 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52428 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52427 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52424 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48730 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48729 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48728 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48727 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48726 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47214 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47213 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47212 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47211 3 Oct 2025 5.2.x < 5.2.6.3195 build 20250715; h5.2.x < h5.2.6.3195 build 20250715 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-33032 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < QuTS hero h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following version:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-30274 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-30273 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-30272 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-30271 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-30270 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-30268 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-30267 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-30265 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-30264 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-29882 29 Aug 2025 QTS: 5.2.x < 5.2.5.3145 build 20250526; QuTS hero: h5.2.x < h5.2.5.3138 build 20250519 We have already fixed the vulnerability in the following versions:; QTS 5.2.5.3145 build 20250526 and later; QuTS hero h5.2.5.3138 build 20250519 and later Update reference ↗
CVE-2025-22481 6 Jun 2025 5.2.x < 5.2.4.3079 build 20250321; h5.2.x < h5.2.4.3079 build 20250321 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-56805 6 Jun 2025 5.2.x < 5.2.4.3079 build 20250321; h5.2.x < h5.2.4.3079 build 20250321 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-53699 7 Mar 2025 5.2.x < 5.2.3.3006 build 20250108; h5.2.x < h5.2.3.3006 build 20250108 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-53698 7 Mar 2025 5.2.x < 5.2.3.3006 build 20250108; h5.2.x < h5.2.3.3006 build 20250108 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-53697 7 Mar 2025 5.2.x < 5.2.3.3006 build 20250108; h5.2.x < h5.2.3.3006 build 20250108 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-53693 7 Mar 2025 5.2.x < 5.2.3.3006 build 20250108; h5.2.x < h5.2.3.3006 build 20250108 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-53692 7 Mar 2025 5.2.x < 5.2.3.3006 build 20250108; h5.2.x < h5.2.3.3006 build 20250108 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50405 7 Mar 2025 5.2.x < 5.2.3.3006 build 20250108; h5.2.x < h5.2.3.3006 build 20250108 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-38638 7 Mar 2025 5.1.x < 5.1.9.2954 build 20241120; h5.1.x < h5.1.9.2954 build 20241120 5.2.x; h5.2.x Update reference ↗
CVE-2024-13086 7 Mar 2025 5.x < QTS 5.2.0.2851 build 20240808; h5.x < QuTS hero h5.2.0.2851 build 20240808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-27600 19 Dec 2024 5.0.x < 5.0.1.2277; 4.5.x < 4.5.4.2280 build 20230112; h5.0.x < h5.0.1.2277 build 20230112; 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-2024-50403 6 Dec 2024 5.2.x < 5.2.2.2950 build 20241114; 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-50402 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-50393 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 5.0.x; 4.5.x Update reference ↗
CVE-2024-48868 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-48867 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

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.