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

ASUSTOR Inc.

ADM

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 adm, 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-2026-105324 7 Oct 2026 ADM: 5.0.0 ≤ 5.1.4.RL21, 4.1.0 ≤ 4.3.3.RWC1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67248 30 Jul 2026 5.0.0 ≤ 5.1.3.RI81; 4.1.0 ≤ 4.3.3.RUN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67247 30 Jul 2026 5.0.0 ≤ 5.1.3.RI81; 4.1.0 ≤ 4.3.3.RUN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67246 30 Jul 2026 5.0.0 ≤ 5.1.3.RI81; 4.1.0 ≤ 4.3.3.RUN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67245 30 Jul 2026 5.0.0 ≤ 5.1.3.RI81; 4.1.0 ≤ 4.3.3.RUN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67244 30 Jul 2026 5.0.0 ≤ 5.1.3.RI81; 4.1.0 ≤ 4.3.3.RUN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-18188 30 Jul 2026 5.0.0 ≤ 5.1.3.RI81; 4.1.0 ≤ 4.3.3.RUN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-18187 30 Jul 2026 5.0.0 ≤ 5.1.3.RI81; 4.1.0 ≤ 4.3.3.RUN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-18186 30 Jul 2026 5.0.0 ≤ 5.1.3.RI81; 4.1.0 ≤ 4.3.3.RUN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-6644 20 Apr 2026 4.1.0 ≤ 4.3.3.RR42; 5.0.0 ≤ 5.1.2.REO1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-6643 20 Apr 2026 4.1.0 ≤ 4.3.3.RR42; 5.0.0 ≤ 5.1.2.REO1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3179 25 Feb 2026 4.1.0 ≤ 4.3.3.ROF1; 5.0.0 ≤ 5.1.2.RE51 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-3100 25 Feb 2026 4.1.0 ≤ 4.3.3.ROF1; 5.0.0 ≤ 5.1.2.RE51 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-24936 3 Feb 2026 4.1.0 ≤ 4.3.3.ROF1; 5.0.0 ≤ 5.1.1.RCI1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24935 3 Feb 2026 4.1.0 ≤ 4.3.3.ROF1; 5.0.0 ≤ 5.1.1.RCI1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24934 3 Feb 2026 4.1.0 ≤ 4.3.3.ROF1; 5.0.0 ≤ 5.1.1.RCI1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24933 3 Feb 2026 4.1.0 ≤ 4.3.3.ROF1; 5.0.0 ≤ 5.1.1.RCI1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24932 3 Feb 2026 4.1.0 ≤ 4.3.3.ROF1; 5.0.0 ≤ 5.1.1.RCI1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13053 12 Dec 2025 ADM: 4.1.0 ≤ 4.3.3.RKD2, 5.0.0 ≤ 5.1.0.RN42 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13052 12 Dec 2025 ADM: 4.1.0 ≤ 4.3.3.RKD2, 5.0.0 ≤ 5.1.0.RN42 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7699 16 Jul 2025 4.1.0 ≤ 4.3.3.RH61; 5.0.0 ≤ 5.0.0.RIN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7618 14 Jul 2025 4.1.0 ≤ 4.3.3.RH61; 5.0.0 ≤ 5.0.0.RIN1; 1.0.0 ≤ 1.0.0.r112 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7380 14 Jul 2025 4.1.0 ≤ 4.3.3.RH61; 5.0.0 ≤ 5.0.0.RIN1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7379 9 Jul 2025 1.1.0 < 1.1.0.r207; 1.2.0 < 1.2.0.r206 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7378 9 Jul 2025 4.1 < 4.3.1.R5A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4475 22 Aug 2023 4.0 ≤ 4.0.6.RIS1; 4.1 ≤ 4.1.0.RLQ1; 4.2 ≤ 4.2.2.RI61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3699 22 Aug 2023 4.0 ≤ 4.0.6.RIS1; 4.1 ≤ 4.1.0.RLQ1; 4.2 ≤ 4.2.2.RI61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3698 17 Aug 2023 4.0 ≤ 4.0.6.RIS1; 4.1 ≤ 4.1.0.RLQ1; 4.2 ≤ 4.2.2.RI61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3697 17 Aug 2023 4.0 ≤ 4.0.6.RIS1; 4.1 ≤ 4.1.0.RLQ1; 4.2 ≤ 4.2.2.RI61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2910 17 Aug 2023 4.0 ≤ 4.0.6.RIS1; 4.1 ≤ 4.1.0.RLQ1; 4.2 ≤ 4.2.2.RI61 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2909 31 May 2023 4.0 ≤ 4.0.6.REG2; 4.1 ≤ 4.1.0.RLQ1; 4.2 ≤ 4.2.1.RGE2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2509 17 May 2023 4.0 ≤ 4.0.6.REG2; 4.1 ≤ 4.1.0.RLQ1; 4.2 ≤ 4.2.1.RGE2; 2.0 ≤ 2.0.0.R129; 2.3 ≤ 2.3.0.r1027 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-30770 17 Apr 2023 4.0 ≤ 4.0.6.REG2; 4.1 ≤ 4.1.0.RLQ1; 4.2 ≤ 4.2.0.RE71 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-37398 5 Aug 2022 3.5 ≤ 3.5.9.RUE3; 4.0 ≤ 4.0.5.RVI1; 4.1 ≤ 4.1.0.RJD1 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.