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

Tenda

AC15

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-11493 8 Jun 2026 15.03.05.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5830 9 Apr 2026 15.03.05.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4975 27 Mar 2026 15.03.05.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3400 1 Mar 2026 15.13.07.0; 15.13.07.1; 15.13.07.2; 15.13.07.3; 15.13.07.4; 15.13.07.5; 15.13.07.6; 15.13.07.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-11389 7 Oct 2025 15.03.05.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-11388 7 Oct 2025 15.03.05.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-11387 7 Oct 2025 15.03.05.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-11386 7 Oct 2025 15.03.05.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8979 14 Aug 2025 15.13.07.13 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5851 8 Jun 2025 15.03.05.19_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5850 8 Jun 2025 15.03.05.19_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5849 8 Jun 2025 15.03.05.19_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5848 8 Jun 2025 15.03.05.19_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-3786 18 Apr 2025 15.03.05.0; 15.03.05.1; 15.03.05.2; 15.03.05.3; 15.03.05.4; 15.03.05.5; 15.03.05.6; 15.03.05.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0566 19 Jan 2025 15.13.07.13 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-10662 1 Nov 2024 15.03.05.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-10661 1 Nov 2024 15.03.05.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2855 24 Mar 2024 15.03.05.18; 15.03.05.19; 15.03.20 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2852 24 Mar 2024 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2851 24 Mar 2024 15.03.05.18; 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2850 24 Mar 2024 15.03.05.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2817 22 Mar 2024 15.03.05.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2816 22 Mar 2024 15.03.05.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2815 22 Mar 2024 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2814 22 Mar 2024 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2813 22 Mar 2024 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2812 22 Mar 2024 15.03.05.18; 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2811 22 Mar 2024 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2810 22 Mar 2024 15.03.05.18; 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2809 22 Mar 2024 15.03.05.18; 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2808 22 Mar 2024 15.03.05.18; 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2807 22 Mar 2024 15.03.05.18; 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2806 22 Mar 2024 15.03.05.18; 15.03.20_multi No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2805 22 Mar 2024 15.03.05.18; 15.03.20_multi 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.