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

Cisco

Cisco Application Policy Infrastructure Controller (APIC)

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-76500 7 Oct 2026 Cisco Application Policy Infrastructure Controller (APIC): 5.2(1g), 5.2(2e), 5.2(2f), 5.2(2g), 5.2(2h), 5.2(3f), 5.2(3e), 5.2(3g), 5.2(4d), 5.2(4e), 5.2(5d), 5.2(5c), 6.0(1g), 5.2(5e), 5.2(4f), 5.2(6e), 6.0(1j), 5.2(6g), 5.2(7f), 5.2(7g), 6.0(2h), 5.2(6h), 5.2(4h), 5.2(8d), 6.0(2j), 5.2(8e), 6.0(3d), 6.0(3e), 5.2(8f), 5.2(8g), 5.3(1d), 5.2(8h), 6.0(4c), 5.3(2a), 5.2(8i), 6.0(5h), 5.3(2b), 6.0(3g), 6.0(5j), 5.3(2c), 6.0(6c), 6.1(1f), 6.0(7e), 5.3(2d), 6.0(8d), 6.0(8e), 6.1(2f), 6.0(8f), 5.3(2e), 6.1(2g), 5.3(2f), 6.0(9c), 6.1(3f), 6.0(9d), 6.0(6g), 6.0(6h), 6.0(8h), 6.1(3g), 6.1(4h), 6.0(9e), 6.1(5e), 6.2(1f), 6.2(1g), 6.0(9f), 6.2(2e) No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-76498 7 Oct 2026 Cisco Application Policy Infrastructure Controller (APIC): 5.2(1g), 5.2(2e), 5.2(2f), 5.2(2g), 5.2(2h), 5.2(3f), 5.2(3e), 5.2(3g), 5.2(4d), 5.2(4e), 5.2(5d), 5.2(5c), 6.0(1g), 5.2(5e), 5.2(4f), 5.2(6e), 6.0(1j), 5.2(6g), 5.2(7f), 5.2(7g), 6.0(2h), 5.2(6h), 5.2(4h), 5.2(8d), 6.0(2j), 5.2(8e), 6.0(3d), 6.0(3e), 5.2(8f), 5.2(8g), 5.3(1d), 5.2(8h), 6.0(4c), 5.3(2a), 5.2(8i), 6.0(5h), 5.3(2b), 6.0(3g), 6.0(5j), 5.3(2c), 6.0(6c), 6.1(1f), 6.0(7e), 5.3(2d), 6.0(8d), 6.0(8e), 6.1(2f), 6.0(8f), 5.3(2e), 6.1(2g), 5.3(2f), 6.0(9c), 6.1(3f), 6.0(9d), 6.0(6g), 6.0(6h), 6.0(8h), 6.1(3g), 6.1(4h), 6.0(9e), 6.1(5e), 6.2(1f), 6.2(1g), 6.0(9f), 6.2(2e) No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-76499 7 Oct 2026 Cisco Application Policy Infrastructure Controller (APIC): 5.2(1g), 5.2(2e), 5.2(2f), 5.2(2g), 5.2(2h), 5.2(3f), 5.2(3e), 5.2(3g), 5.2(4d), 5.2(4e), 5.2(5d), 5.2(5c), 6.0(1g), 5.2(5e), 5.2(4f), 5.2(6e), 6.0(1j), 5.2(6g), 5.2(7f), 5.2(7g), 6.0(2h), 5.2(6h), 5.2(4h), 5.2(8d), 6.0(2j), 5.2(8e), 6.0(3d), 6.0(3e), 5.2(8f), 5.2(8g), 5.3(1d), 5.2(8h), 6.0(4c), 5.3(2a), 5.2(8i), 6.0(5h), 5.3(2b), 6.0(3g), 6.0(5j), 5.3(2c), 6.0(6c), 6.1(1f), 6.0(7e), 5.3(2d), 6.0(8d), 6.0(8e), 6.1(2f), 6.0(8f), 5.3(2e), 6.1(2g), 5.3(2f), 6.0(9c), 6.1(3f), 6.0(9d), 6.0(6g), 6.0(6h), 6.0(8h), 6.1(3g), 6.1(4h), 6.0(9e), 6.1(5e), 6.2(1f), 6.2(1g), 6.0(9f), 6.2(2e) No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-76488 7 Oct 2026 Cisco Application Policy Infrastructure Controller (APIC): 5.2(1g), 5.2(2e), 5.2(2f), 5.2(2g), 5.2(2h), 5.2(3f), 5.2(3e), 5.2(3g), 5.2(4d), 5.2(4e), 5.2(5d), 5.2(5c), 6.0(1g), 5.2(5e), 5.2(4f), 5.2(6e), 6.0(1j), 5.2(6g), 5.2(7f), 5.2(7g), 6.0(2h), 5.2(6h), 5.2(4h), 5.2(8d), 6.0(2j), 5.2(8e), 6.0(3d), 6.0(3e), 5.2(8f), 5.2(8g), 5.3(1d), 5.2(8h), 6.0(4c), 5.3(2a), 5.2(8i), 6.0(5h), 5.3(2b), 6.0(3g), 6.0(5j), 5.3(2c), 6.0(6c), 6.1(1f), 6.0(7e), 5.3(2d), 6.0(8d), 6.0(8e), 6.1(2f), 6.0(8f), 5.3(2e), 6.1(2g), 5.3(2f), 6.0(9c), 6.0(9d), 6.0(6g), 6.0(6h), 6.0(8h), 6.0(9e), 6.0(9f) No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-20321 7 Oct 2026 Cisco Application Policy Infrastructure Controller (APIC): 5.3(1d), 5.3(2a), 5.3(2b), 5.3(2c), 5.3(2d), 5.3(2e), 5.3(2f), 6.1(5e), 6.2(1f), 6.2(1g), 6.2(2e) No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-20107 25 Feb 2026 6.1(1f); 6.1(2f); 6.1(2g); 6.1(3f); 6.1(3g) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20119 26 Feb 2025 3.2(8d); 3.2(1m); 3.2(5e); 4.1(2m); 3.2(41d); 3.2(3s); 4.0(3c); 4.1(1k) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20118 26 Feb 2025 3.2(8d); 3.2(1m); 3.2(5e); 4.1(2m); 3.2(41d); 3.2(3s); 4.0(3c); 4.1(1k) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20117 26 Feb 2025 3.2(8d); 3.2(1m); 3.2(5e); 4.1(2m); 3.2(41d); 3.2(3s); 4.0(3c); 4.1(1k) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20116 26 Feb 2025 3.2(8d); 3.2(1m); 3.2(5e); 4.1(2m); 3.2(41d); 3.2(3s); 4.0(3c); 4.1(1k) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20478 28 Aug 2024 3.2(8d); 2.2(1o); 1.2(2h); 2.2(2i); 1.2(1k); 2.2(1k); 3.1(2m); 3.2(1m) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20279 28 Aug 2024 3.2(8d); 2.2(1o); 1.2(2h); 2.2(2i); 1.2(1k); 2.2(1k); 3.1(2m); 3.2(1m) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20230 23 Aug 2023 5.2(6e); 5.2(6g); 5.2(7f); 5.2(7g); 6.0(1g); 6.0(1j); 6.0(2h); 6.0(2j) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-20011 23 Feb 2023 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1582 25 Aug 2021 n/a An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-1581 25 Aug 2021 n/a An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-1580 25 Aug 2021 n/a An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-1579 25 Aug 2021 n/a An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-1578 25 Aug 2021 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-1577 25 Aug 2021 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-3335 3 Jun 2020 n/a An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-3333 3 Jun 2020 n/a An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-3139 26 Jan 2020 prior to 4.2(3j) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-1889 4 Jul 2019 unspecified < 4.1(2g) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-1838 3 May 2019 unspecified < 4.1(1i) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-1692 3 May 2019 unspecified < 4.1(1i) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-1682 3 May 2019 unspecified < 4.1(1i) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-1586 3 May 2019 unspecified < 4.2(0.33c) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-1587 3 May 2019 unspecified < 4.2(0.33c) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-1690 11 Mar 2019 unspecified < 4.2(0.21c) 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.