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

Arista Networks

EOS

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at eos, 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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2025-8870 14 Nov 2025 EOS: 4.34.2FX The recommended resolution is to upgrade to a remediated software version at your earliest convenience. Arista recommends customers move to the latest version of each release that contains all the fixes listed below. For more information about upgrading see EOS User Manual: Upgrades and Downgrades https://www.arista.com/en/um-eos/eos-upgrades-and-downgrades; CVE-2025-8870 has been fixed in the following releases:; * 4.35.0F and later releases Update reference ↗
CVE-2025-6188 25 Aug 2025 4.33.0 ≤ 4.33.1F; 4.33.1.0 ≤ 4.33.1.2F; 4.32.4.0 ≤ 4.32.4.1M; 4.31.0 ≤ 4.31.6M; 4.30.0 ≤ 4.30.9.1M No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-3456 25 Aug 2025 4.34.0F; 4.33.0 ≤ 4.33.3F; 4.32.0 ≤ 4.32.5M; 4.31.0 ≤ 4.31.7M; 4.30.0 ≤ 4.30.10M; 4.29.0 ≤ 4.29.10M No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-2826 27 May 2025 4.33.2F No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-2796 27 May 2025 4.33.0 ≤ 4.33.2F No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-11185 27 May 2025 4.29.0 ≤ 4.29.10M; 4.30.0 ≤ 4.30.9M; 4.31.0 ≤ 4.31.6M; 4.32.0 ≤ 4.32.3M; 4.33.0 ≤ 4.33.1F No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9448 8 May 2025 4.33.0 ≤ 4.33.0F; 4.32.0 ≤ 4.32.3M; 4.31.0 ≤ 4.31.5M; 4.30.0 ≤ 4.30.8M No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0936 7 May 2025 4.33.0 ≤ 4.33.1; 4.32.0 ≤ 4.32.3M; 4.31.0 ≤ 4.31.5M; 4.30.1F ≤ 4.30.9M No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8000 4 Mar 2025 4.32.0 ≤ 4.32.4M; 4.31.0 ≤ 4.31.5M; 4.30.0 ≤ 4.30.8M No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9135 4 Mar 2025 4.33.0; 4.31.0 ≤ 4.31.5; 4.30.0 ≤ 4.30.8.1; 4.29.0 ≤ 4.29.9.1; 4.28.0; 4.27.0 ≤ 4.27.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-1260 4 Mar 2025 4.33.0 ≤ 4.33.1; 4.32.0 ≤ 4.32.3; 4.31.0 ≤ 4.31.5; 4.30.0 ≤ 4.30.8; 4.29.0 ≤ 4.29.9; 4.28.0 ≤ 4.28.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-1259 4 Mar 2025 4.33.0 ≤ 4.33.1; 4.32.0 ≤ 4.32.3; 4.31.0 ≤ 4.31.5; 4.30.0 ≤ 4.30.8; 4.29.0 ≤ 4.29.9; 4.28.0 ≤ 4.28.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-5872 10 Jan 2025 4.32.0F ≤ 4.32.2F; 4.31.0M ≤ 4.31.4M; 4.30.0M ≤ 4.30.7M; 4.29.0M ≤ 4.29.8M; 4.28.1F ≤ 4.28.11F No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-7095 10 Jan 2025 4.32.0F ≤ 4.32.2F; 4.31.0M ≤ 4.31.4M; 4.30.0M ≤ 4.30.7M; 4.29.0; 4.28.0; 4.27.0; 4.26.0; 4.25.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3646 29 Aug 2023 4.28.2F ≤ 4.28.5.1M ; 4.29.0 ≤ 4.29.1F No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-24548 29 Aug 2023 4.25.0F ≤ =4.25.0F; 4.24.0 ≤ <=4.24.11M; 4.23.0 ≤ <=4.23.14M; 4.22.1F ≤ <=4.22.13M No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-24545 12 Apr 2023 4.29.0 ≤ 4.29.1F; 4.28.0 ≤ 4.28.4M; 4.27.0 ≤ 4.27.7M; 4.26.8M ≤ 4.26.8M 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-2023-24513 12 Apr 2023 4.29.0 ≤ 4.29.1F; 4.28.0 ≤ 4.28.5M; 4.27.0 ≤ 4.27.8M; 4.26.0 ≤ 4.26.9M 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-2023-24511 12 Apr 2023 4.28.0 4.28.5.1M; 4.27.0 4.27.8.1M; 4.26.0 4.26.9M; 4.25.0 4.25.10M; 4.24.0 4.24.11M; 4.29.0 ≤ 4.29.1F 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-28510 24 Jan 2023 4.22; 4.27.1 ≤ 4.27.0; 4.26.4 ≤ 4.26.0; 4.25.6 ≤ 4.25.0; 4.24.8 ≤ 4.24.0; 4.23.10 ≤ 4.23.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2021-28511 5 Aug 2022 4.24.0 ≤ 4.24.9; 4.25.0 ≤ 4.25.8; 4.26.0 ≤ 4.26.5; 4.27.0 ≤ 4.27.3 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2021-28505 14 Apr 2022 4.26.3M ≤ 4.26.0; 4.27.0F ≤ 4.27.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-28504 1 Apr 2022 4.26.3F ≤ 4.26.0; 4.27.0F ≤ 4.27.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2021-28507 14 Jan 2022 4.22.x; 4.26.2F ≤ 4.26.0; 4.25.5.1M ≤ 4.25.5; 4.25.4M ≤ 4.25.4; 4.25.3 ≤ 4.25.0; 4.24.7M ≤ 4.24.0; 4.23.9M ≤ 4.23.0; 4.21.x ≤ 4.21.x 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-28506 14 Jan 2022 4.26.2F ≤ 4.26.0; 4.25.5.1M ≤ 4.25.5; 4.25.4M ≤ 4.25.4; 4.25.3 ≤ 4.25.0; 4.24.7M ≤ 4.24.2F 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 ↗

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.