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

Tenda

AC10U

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-2025-15218 30 Dec 2025 AC10U: 15.03.06.48, 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-15215 30 Dec 2025 AC10U: 15.03.06.48, 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2853 24 Mar 2024 15.03.06.48; 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2764 21 Mar 2024 15.03.06.48 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2763 21 Mar 2024 15.03.06.48 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2711 20 Mar 2024 15.03.06.48 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2710 20 Mar 2024 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2709 20 Mar 2024 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2708 20 Mar 2024 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2707 20 Mar 2024 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2706 20 Mar 2024 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2705 20 Mar 2024 1.0; 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2704 20 Mar 2024 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-2703 20 Mar 2024 15.03.06.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0932 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0931 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0930 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0929 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0928 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0927 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0926 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0925 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0924 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0923 26 Jan 2024 15.03.06.49_multi_TDE01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0922 26 Jan 2024 15.03.06.49_multi_TDE01 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.