← Search results
CVE-LINKED INVENTORY20 SECURITY RECORDS
ASUS
Router
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 router, 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-14911 | 7 Oct 2026 | Router: 3.0.0.6.102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-19396 | 7 Oct 2026 | Router: 3.0.0.6_102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-19386 | 7 Oct 2026 | Router: 3.0.0.6.102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-16528 | 7 Oct 2026 | Router: 3.0.0.4.386 series, 3.0.0.4.388 series, 3.0.0.6.102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-13313 | 1 Oct 2026 | Router: 3.0.0.4_386 series, 3.0.0.4_388 series, 3.0.0.6_102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-14157 | 1 Oct 2026 | Router: 3.0.0.6_102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-13385 | 15 Jul 2026 | 3.0.0.4_386 series; 3.0.0.4_388 series; 3.0.0.6_102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-11851 | 15 Jul 2026 | ASUSWRT 3.0.0.4_386 series; ASUSWRT 3.0.0.4_388 series; ASUSWRT 3.0.0.6_102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-15101 | 26 Mar 2026 | 3.0.0.6_102 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59372 | 25 Nov 2025 | 3.0.0.4_386; 3.0.0.4_388; 3.0.0.6_102 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59371 | 25 Nov 2025 | 3.0.0.4_386; 3.0.0.4_388; 3.0.0.6_102 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59370 | 25 Nov 2025 | 3.0.0.4_386; 3.0.0.4_388; 3.0.0.6_102 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59369 | 25 Nov 2025 | 3.0.0.4_386; 3.0.0.4_388; 3.0.0.6_102 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59368 | 25 Nov 2025 | 3.0.0.4_386; 3.0.0.4_388; 3.0.0.6_102 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-12003 | 25 Nov 2025 | 3.0.0.4_386; 3.0.0.4_388; 3.0.0.6_102 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59365 | 25 Nov 2025 | 3.0.0.4_386; 3.0.0.4_388; 3.0.0.6_102 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59366 | 25 Nov 2025 | 3.0.0.4_386; 3.0.0.4_388; 3.0.0.6_102 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-2492 | 18 Apr 2025 | 3.0.0.4_382 series; 3.0.0.4_386 series; 3.0.0.4_388 series; 3.0.0.6_102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-13062 | 2 Jan 2025 | 3.0.0.4_382 series; 3.0.0.4_386 series; 3.0.0.4_388 series; 3.0.0.6_102 series | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-12912 | 2 Jan 2025 | 3.0.0.4_382 series; 3.0.0.4_386 series; 3.0.0.4_388 series; 3.0.0.6_102 series | 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.