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

QNAP Systems Inc.

File Station 5

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

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

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-2026-26240 10 Jun 2026 5.5.0 < 5.5.6.5243 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-26241 10 Jun 2026 5.5.0 < 5.5.6.5243 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24724 10 Jun 2026 5.5.0 < 5.5.6.5243 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-26239 10 Jun 2026 5.5.0 < 5.5.6.5208 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24720 10 Jun 2026 5.5.0 < 5.5.6.5243 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22899 10 Jun 2026 5.5.0 < 5.5.6.5208 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54155 11 Feb 2026 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54161 11 Feb 2026 5.5.x < 5.5.6.5068 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54162 11 Feb 2026 5.5.x < 5.5.6.5068 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54163 11 Feb 2026 5.5.x < 5.5.6.5166 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54169 11 Feb 2026 5.5.x < 5.5.6.5068 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-57707 11 Feb 2026 5.5.x < 5.5.6.5166 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-57713 11 Feb 2026 5.5.x < 5.5.6.5166 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-62853 11 Feb 2026 5.5.x < 5.5.6.5166 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-62854 11 Feb 2026 5.5.x < 5.5.6.5190 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-62855 11 Feb 2026 5.5.x < 5.5.6.5190 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-62856 11 Feb 2026 5.5.x < 5.5.6.5190 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66278 11 Feb 2026 5.5.x < 5.5.6.5190 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22894 11 Feb 2026 5.5.x < 5.5.6.5190 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47207 7 Nov 2025 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52865 7 Nov 2025 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-53408 7 Nov 2025 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-53409 7 Nov 2025 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-53410 7 Nov 2025 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-53411 7 Nov 2025 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-53412 7 Nov 2025 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-53413 7 Nov 2025 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-57706 7 Nov 2025 5.5.x < 5.5.6.5018 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29900 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29899 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29890 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29889 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29888 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29886 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29879 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29878 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29875 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29874 29 Aug 2025 5.5.x < 5.5.6.4907 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29901 26 Aug 2025 5.5.x < 5.5.6.4933 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47206 18 Aug 2025 5.5.x < 5.5.6.4933 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29885 6 Jun 2025 5.5.x < 5.5.6.4791 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29884 6 Jun 2025 5.5.x < 5.5.6.4791 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29883 6 Jun 2025 5.5.x < 5.5.6.4791 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-22486 6 Jun 2025 5.5.x < 5.5.6.4791 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-22484 6 Jun 2025 5.5.x < 5.5.6.4847 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-22490 6 Jun 2025 5.5.x < 5.5.6.4847 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29871 6 Jun 2025 5.5.x < 5.5.6.4847 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29872 6 Jun 2025 5.5.x < 5.5.6.4847 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29873 6 Jun 2025 5.5.x < 5.5.6.4847 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-29876 6 Jun 2025 5.5.x < 5.5.6.4847 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.