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

Cisco

Cisco IOS XE Software

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-20214 7 May 2025 17.11.1; 17.11.1a; 17.12.1; 17.12.1w; 17.12.1a; 17.12.1x; 17.12.2; 17.12.2a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20434 25 Sep 2024 16.6.1; 16.6.2; 16.6.3; 16.6.4; 16.6.5; 16.6.4a; 16.6.6; 16.6.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20510 25 Sep 2024 16.3.1; 16.3.2; 16.3.3; 16.3.1a; 16.3.4; 16.3.5; 16.3.5b; 16.3.6 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-20467 25 Sep 2024 17.12.1; 17.12.1a; 17.11.99SW No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20464 25 Sep 2024 17.13.1; 17.13.1a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20480 25 Sep 2024 16.1.1; 16.1.2; 16.1.3; 16.2.1; 16.2.2; 16.3.1; 16.3.2; 16.3.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20437 25 Sep 2024 17.3.2; 17.3.3; 17.3.2a; 17.3.4; 17.3.5; 17.3.4a; 17.3.6; 17.3.4b No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20436 25 Sep 2024 3.9.1S; 3.9.2S; 3.9.0aS; 3.10.0S; 3.10.1S; 3.10.2S; 3.10.3S; 3.10.4S No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20455 25 Sep 2024 17.1.1; 17.1.1a; 17.1.1s; 17.1.1t; 17.1.3; 17.2.1; 17.2.1r; 17.2.1a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20313 24 Apr 2024 17.5.1; 17.5.1a; 17.6.1; 17.6.2; 17.6.1w; 17.6.1a; 17.6.1x; 17.6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20310 3 Apr 2024 N/A; 10.5(1); 10.5(2); 10.5(2a); 10.5(2b); 10.5(2)SU3; 10.5(2)SU2a; 10.5(2)SU4a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20265 27 Mar 2024 N/A; 8.2.100.0; 8.2.130.0; 8.2.111.0; 8.2.110.0; 8.2.121.0; 8.2.141.0; 8.2.151.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-20309 27 Mar 2024 3.7.0S; 3.7.1S; 3.7.2S; 3.7.3S; 3.7.4S; 3.7.5S; 3.7.6S; 3.7.7S No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20303 27 Mar 2024 17.2.1; 17.2.1r; 17.2.1a; 17.2.1v; 17.2.2; 17.2.3; 17.3.1; 17.3.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20278 27 Mar 2024 17.6.1; 17.6.2; 17.6.1w; 17.6.1a; 17.6.1x; 17.6.3; 17.6.1y; 17.6.1z No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20306 27 Mar 2024 17.10.1; 17.10.1a; 17.10.1b; 17.11.1; 17.11.1a; 17.12.1; 17.12.1w; 17.12.1a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20314 27 Mar 2024 16.1.1; 16.1.2; 16.1.3; 16.2.1; 16.2.2; 16.3.1; 16.3.2; 16.3.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20324 27 Mar 2024 16.10.1; 16.10.1s; 16.10.1e; 16.11.1; 16.11.1a; 16.11.1b; 16.11.2; 16.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20259 27 Mar 2024 17.1.1; 17.1.1a; 17.1.1s; 17.1.1t; 17.1.3; 17.2.1; 17.2.1r; 17.2.1a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20316 27 Mar 2024 16.3.1; 16.3.2; 16.3.3; 16.3.1a; 16.3.4; 16.3.5; 16.3.5b; 16.3.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20235 4 Oct 2023 17.3.1; 17.3.2; 17.3.3; 17.3.1a; 17.3.1w; 17.3.2a; 17.3.1x; 17.3.1z No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20202 27 Sep 2023 17.10.1; 17.10.1a; 17.10.1b; 17.9.1; 17.9.1w; 17.9.2; 17.9.1a; 17.9.1x No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20227 27 Sep 2023 16.8.1; 16.8.1a; 16.8.1b; 16.8.1s; 16.8.1c; 16.8.1d; 16.8.2; 16.8.1e No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-20226 27 Sep 2023 17.7.1; 17.7.1a; 17.7.2; 17.10.1; 17.10.1a; 17.8.1; 17.8.1a; 17.9.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20033 27 Sep 2023 16.3.1; 16.3.2; 16.3.3; 16.3.1a; 16.3.4; 16.3.5; 16.3.5b; 16.3.6 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-20187 27 Sep 2023 3.7.1S; 3.7.2S; 3.7.3S; 3.7.4S; 3.7.5S; 3.7.6S; 3.7.7S; 3.7.2tS No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-20231 27 Sep 2023 16.12.8; 16.12.4; 16.12.4a; 16.12.5; 16.12.6; 16.12.5a; 16.12.5b; 16.12.6a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20100 23 Mar 2023 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20072 23 Mar 2023 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20067 23 Mar 2023 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20066 23 Mar 2023 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20065 23 Mar 2023 16.4.1; 16.4.2; 16.4.3; 17.3.1; 17.3.2; 17.3.3; 17.3.1a; 17.3.1w No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20035 23 Mar 2023 n/a No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-20029 23 Mar 2023 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20027 23 Mar 2023 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20864 10 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20837 10 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20915 10 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20870 10 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20944 10 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20856 30 Sep 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20855 30 Sep 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20851 30 Sep 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20848 30 Sep 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20847 30 Sep 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20810 30 Sep 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20676 15 Apr 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20678 15 Apr 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20679 15 Apr 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-20681 15 Apr 2022 n/a 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.