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

Tenda

FH451

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-4535 22 Mar 2026 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4534 22 Mar 2026 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3679 7 Mar 2026 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3678 7 Mar 2026 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3677 7 Mar 2026 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2911 22 Feb 2026 1.0.0.0; 1.0.0.1; 1.0.0.2; 1.0.0.3; 1.0.0.4; 1.0.0.5; 1.0.0.6; 1.0.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7855 19 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7854 19 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7853 19 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7807 18 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7806 18 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7805 18 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7796 18 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7795 18 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7794 18 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7793 18 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7792 18 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7747 17 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7506 12 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7505 12 Jul 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7434 11 Jul 2025 1.0.0.0; 1.0.0.1; 1.0.0.2; 1.0.0.3; 1.0.0.4; 1.0.0.5; 1.0.0.6; 1.0.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5080 22 May 2025 1.0.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-12002 30 Nov 2024 20241129 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.