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

D-Link

DNS-120

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-16448 21 Jul 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5312 1 Apr 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5311 1 Apr 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5215 31 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5214 31 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5213 31 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5212 31 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5211 31 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4214 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4213 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4212 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4211 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4210 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4209 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4207 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4206 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4205 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4204 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4203 16 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4197 15 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4196 15 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4195 15 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4194 15 Mar 2026 20260205 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8214 27 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8213 27 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8212 27 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8211 27 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8210 27 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8134 24 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8133 24 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8132 24 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8131 24 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8130 24 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8129 24 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8128 24 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8127 24 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7922 19 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7849 15 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7832 15 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7831 15 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7830 15 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7829 15 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7828 15 Aug 2024 20240814 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7715 13 Aug 2024 20240812 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.