← 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.
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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2024-38639 | 18 Sep 2026 | See the vendor and CVE records for the affected range. | QTS: ? | Update reference ↗ |
| CVE-2026-24719 | 10 Jun 2026 | 5.2.0 < 5.2.9.3492 build 20260507; h5.2.0 < h5.2.9.3499 build 20260514 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-24717 | 10 Jun 2026 | 5.2.0 < 5.2.9.3492 build 20260507; h5.2.0 < h5.2.9.3499 build 20260514; h5.3.0 < h5.3.4.3500 build 20260520; ? < h6.0.0.3459 build 20260409 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-24716 | 10 Jun 2026 | 5.2.0 < 5.2.9.3492 build 20260507; h5.2.0 < h5.2.9.3499 build 20260514; h5.3.0 < h5.3.4.3500 build 20260520; ? < h6.0.0.3459 build 20260409 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-22893 | 10 Jun 2026 | 5.2.0 < 5.2.9.3410 build 20260214; h5.2.0 < h5.2.9.3410 build 20260214; h5.3.0 < h5.3.4.3500 build 20260520; ? < h6.0.0.3459 build 20260409 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66281 | 10 Jun 2026 | 5.2.0 < 5.2.9.3410 build 20260214; h5.2.0 < h5.2.9.3410 build 20260214; h5.3.0 < h5.3.4.3500 build 20260520; ? < h6.0.0.3397 build 20260206 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66280 | 10 Jun 2026 | 5.2.0 < 5.2.9.3410 build 20260214; h5.2.0 < h5.2.9.3410 build 20260214; h5.3.0 < h5.3.4.3500 build 20260520; ? < h6.0.0.3397 build 20260206 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66279 | 10 Jun 2026 | 5.2.0 < 5.2.9.3410 build 20260214; h5.2.0 < h5.2.9.3410 build 20260214; h5.3.0 < h5.3.4.3500 build 20260520; ? < h6.0.0.3397 build 20260206 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66273 | 10 Jun 2026 | 5.2.0 < 5.2.9.3410 build 20260214; h5.2.0 < h5.2.9.3410 build 20260214; h5.3.0 < h5.3.4.3500 build 20260520; ? < h6.0.0.3397 build 20260206 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59382 | 10 Jun 2026 | See the vendor and CVE records for the affected range. | ?; c5.0.0 | Update reference ↗ |
| CVE-2025-66276 | 10 Jun 2026 | 5.2.0 < 5.2.7.3256 build 20250913 | ? | Update reference ↗ |
| CVE-2025-62858 | 9 Jun 2026 | 5.2.0 < 5.2.9.3410 build 20260214; h5.2.0 < h5.2.9.3410 build 20260214; h5.3.0 < h5.3.4.3500 build 20260520; ? < h6.0.0.3397 build 20260206 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-41539 | 9 Jun 2026 | 5.2.0 < 5.2.9.3492 build 20260507; h5.2.0 < h5.2.9.3499 build 20260514; h5.3.0 < h5.3.4.3500 build 20260520; ? < h6.0.0.3500 build 20260520 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-14026 | 11 Mar 2026 | 5.1.x < 5.1.9.2954 build 20241120; 5.2.x < 5.2.3.3006 build 20250108; h5.1.x < h5.1.9.2954 build 20241120; h5.2.x < h5.2.3.3006 build 20250108 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-47205 | 11 Feb 2026 | 5.2.x < 5.2.8.3332 build 20251128; h5.2.x < h5.2.8.3321 build 20251117 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-58466 | 11 Feb 2026 | 5.2.x < 5.2.8.3332 build 20251128; h5.2.x < h5.2.8.3321 build 20251117 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66274 | 11 Feb 2026 | 5.2.0 < 5.2.9.3410 build 20260214; h5.2.0 < h5.2.9.3410 build 20260214; h5.3.0 < h5.3.2.3354 build 20251225; ? < h6.0.0.3397 build 20260206 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66277 | 11 Feb 2026 | 5.2.x < 5.2.8.3350 build 20251216; h5.3.x < h5.3.2.3354 build 20251225; h5.2.x < h5.2.8.3350 build 20251216 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-62852 | 2 Jan 2026 | QTS: 5.2.x < 5.2.8.3332 build 20251128 | We have already fixed the vulnerability in the following version:; QTS 5.2.8.3332 build 20251128 and later | Update reference ↗ |
| CVE-2025-59381 | 2 Jan 2026 | 5.2.0 < 5.2.8.3332 build 20251128; h5.2.0 < h5.2.8.3321 build 20251117; h5.3.0 < h5.3.2.3354 build 20251225 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59380 | 2 Jan 2026 | 5.2.x < 5.2.8.3332 build 20251128; h5.2.x < h5.2.8.3321 build 20251117 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-48721 | 2 Jan 2026 | QTS: 5.2.x < 5.2.8.3332 build 20251128 | We have already fixed the vulnerability in the following version:; QTS 5.2.8.3332 build 20251128 and later | Update reference ↗ |
| CVE-2025-9110 | 2 Jan 2026 | 5.2.x < 5.2.8.3332 build 20251128; h5.2.x < h5.2.8.3321 build 20251117; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-57705 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-54166 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-54165 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-54164 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53596 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53593 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53592 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53591 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912; h5.2.x < h5.2.7.3256 build 20250913 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53590 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53589 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53414 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53405 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-52872 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.0.3192 build 20250716 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-52864 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.0.3192 build 20250716 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-52863 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.0.3192 build 20250716 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-52431 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-52430 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-52426 | 2 Jan 2026 | 5.2.x < 5.2.7.3256 build 20250913; h5.2.x < h5.2.7.3256 build 20250913; h5.3.x < h5.3.1.3250 build 20250912 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-47208 | 2 Jan 2026 | 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-44013 | 2 Jan 2026 | 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-59385 | 16 Dec 2025 | QTS: 5.2.x < 5.2.7.3297 build 20251024; QuTS hero: h5.2.x < h5.2.7.3297 build 20251024, h5.3.x < h5.3.1.3292 build 20251024 | We have already fixed the vulnerability in the following versions:; QTS 5.2.7.3297 build 20251024 and later; QuTS hero h5.2.7.3297 build 20251024 and later; QuTS hero h5.3.1.3292 build 20251024 and later | Update reference ↗ |
| CVE-2025-62847 | 16 Dec 2025 | QTS: 5.2.x < 5.2.7.3297 build 20251024; QuTS hero: h5.2.x < h5.2.7.3297 build 20251024, h5.3.x < h5.3.1.3292 build 20251024 | We have already fixed the vulnerability in the following versions:; QTS 5.2.7.3297 build 20251024 and later; QuTS hero h5.2.7.3297 build 20251024 and later; QuTS hero h5.3.1.3292 build 20251024 and later | Update reference ↗ |
| CVE-2025-62848 | 16 Dec 2025 | QTS: 5.2.x < 5.2.7.3297 build 20251024; QuTS hero: h5.2.x < h5.2.7.3297 build 20251024, h5.3.x < h5.3.1.3292 build 20251024 | We have already fixed the vulnerability in the following versions:; QTS 5.2.7.3297 build 20251024 and later; QuTS hero h5.2.7.3297 build 20251024 and later; QuTS hero h5.3.1.3292 build 20251024 and later | Update reference ↗ |
| CVE-2025-62849 | 16 Dec 2025 | QTS: 5.2.x < 5.2.7.3297 build 20251024; QuTS hero: h5.2.x < h5.2.7.3297 build 20251024, h5.3.x < h5.3.1.3292 build 20251024 | We have already fixed the vulnerability in the following versions:; QTS 5.2.7.3297 build 20251024 and later; QuTS hero h5.2.7.3297 build 20251024 and later; QuTS hero h5.3.1.3292 build 20251024 and later | Update reference ↗ |
| CVE-2025-53407 | 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-53406 | 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-52866 | 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 |
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.