D-Link
DIR-615
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 dir-615, 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-2026-2152 | 8 Feb 2026 | 4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-2151 | 8 Feb 2026 | 4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-1506 | 28 Jan 2026 | 4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-1505 | 28 Jan 2026 | 4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-1448 | 26 Jan 2026 | 4.0; 4.1; 4.2; 4.3; 4.4; 4.5; 4.6; 4.7 | 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.