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

Cisco

Cisco Catalyst SD-WAN Manager

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-20294 5 Aug 2026 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20224 14 May 2026 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20210 14 May 2026 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20209 14 May 2026 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20108 25 Mar 2026 20.12.1; 20.12.1_LI_Images; 20.12.2; 20.12.3; 20.12.3.1; 20.12.4; 20.12.4.1; 20.12.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20129 25 Feb 2026 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20126 25 Feb 2026 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20147 7 May 2025 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20216 7 May 2025 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20187 7 May 2025 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20122 7 May 2025 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20213 7 May 2025 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20157 7 May 2025 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26066 18 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26071 18 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26073 18 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26074 18 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1234 18 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1232 18 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1461 18 Nov 2024 19.2.1; 18.4.4; 19.3.0; 19.2.2; 19.2.099; 18.3.6; 18.3.7; 19.2.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1462 18 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1465 18 Nov 2024 17.2.6; 17.2.7; 17.2.8; 17.2.9; 17.2.10; 17.2.4; 17.2.5; 18.3.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1466 15 Nov 2024 19.2.1; 18.4.4; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2; 19.2.099; 18.3.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1470 15 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1481 15 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1482 15 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1464 15 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1483 15 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1484 15 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1491 15 Nov 2024 20.1.12; 19.2.1; 18.4.4; 18.4.5; 20.1.1.1; 20.1.1; 19.3.0; 19.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20475 25 Sep 2024 20.6.1; 20.6.1.1; 20.6.0.18.3; 20.6.0.18.4; 20.6.1.0.1; 20.6.2; 20.7.1EFT2; 20.7.1 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.