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

D-Link

DI-8100

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-7857 5 May 2026 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7856 5 May 2026 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7855 5 May 2026 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7854 5 May 2026 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7853 5 May 2026 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7851 5 May 2026 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7248 28 Apr 2026 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7247 28 Apr 2026 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10440 15 Sep 2025 16.07.26A1; 17.12.20A1; 19.12.10A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7911 20 Jul 2025 1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7908 20 Jul 2025 1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7790 18 Jul 2025 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7762 17 Jul 2025 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7603 14 Jul 2025 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7602 14 Jul 2025 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6881 30 Jun 2025 16.07.21 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5228 27 May 2025 20250523 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-4883 18 May 2025 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-4544 11 May 2025 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-3538 13 Apr 2025 16.07.26A1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7833 15 Aug 2024 16.07 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7436 3 Aug 2024 16.07 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.