Arista EOS CVE-2025-54545
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as restricted CLI user
-
DeliveryIssue sandbox-breakout command
-
ExploitEscape to system shell
-
ExecutionElevate to full privileges
-
ImpactFull control of device
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Permission assignment review
|
| Exploitation Conditions | Exploitation requires an existing restricted (low-privilege, authenticated per PR:L) user account with CLI access on the affected Arista platform; the attacker leverages the CLI sandbox to break out into the underlying system shell and elevate privileges. Limiting factors: access is LOCAL only (AV:L), so no remote/network exploitation is possible, and the attacker must already possess valid restricted CLI credentials - this confines realistic risk to malicious insiders or attackers who have already obtained a limited foothold, rather than unauthenticated external actors. No user interaction is required (UI:N) and complexity is low (AC:L), so once restricted access is held the breakout is straightforward. |
| Impact | This is a locally-exploitable privilege escalation via CLI sandbox breakout, scored 7.8 (High) with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - meaning an attacker needs local access and existing low-privilege (restricted/authenticated) credentials, but no user interaction, and gains full confidentiality, integrity, and availability impact once the sandbox is escaped. The attack vector is LOCAL, not network, so this is not a remotely wormable mass-exploitation issue; it requires an attacker to already hold a restricted CLI account on the device, which bounds the realistic threat to insiders or an attacker who has already gained a foothold with limited credentials. No EPSS score, CISA KEV listing, or public POC was provided in the intelligence, so there is no signal of active or probable exploitation - consistent with a privilege-escalation primitive that depends on prior access rather than a widely-scanned remote flaw. The CWE-732 (incorrect permission assignment) classification aligns with the sandbox-breakout description. Note a metadata conflict: the single tag is 'Information Disclosure,' but the described impact is sandbox escape and privilege elevation to a system shell, not primarily disclosure - the CVSS confidentiality impact is only one of three equal High impacts. |
| Exploit ScenarioDerived | An attacker who already holds a restricted CLI user account on an affected Arista platform (for example a limited operator or a compromised low-privilege login) issues commands that escape the constrained CLI sandbox and drop into the underlying system shell, then elevates to full privileges. Because the CVSS vector is AV:L/AC:L/PR:L with no user interaction, exploitation is reliable once local restricted access exists. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Privilege escalation in Arista EOS allows a restricted, authenticated CLI user to break out of the CLI sandbox into the underlying system shell and elevate to full privileges. The flaw is scored 7.8 High (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H): exploitation is local, requires an existing valid low-privilege CLI account, needs no user interaction, and is low complexity, delivering high confidentiality, integrity, and availability impact once the sandbox is escaped. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit identified at time of analysis, so realistic risk is confined to malicious insiders or attackers who already hold a limited foothold on the device.
RemediationAI
Apply the fixed EOS release identified in Arista Security Advisory 0124 (https://www.arista.com/en/support/advisories-notices/security-advisory/22538-security-advisory-0124); no specific patched version number is confirmed in the provided data, so consult the advisory for the exact fixed release and required upgrade path before scheduling maintenance, noting that an EOS upgrade entails a device reload/maintenance window and per-platform compatibility checks. Until the upgrade is applied, prioritize compensating controls that remove the prerequisite rather than the bug: audit and minimize the number of accounts holding the restricted CLI role, enforce AAA (TACACS+/RADIUS) with least privilege and per-command authorization, and bind CLI management access to a dedicated management VRF or interface ACLs so only trusted administrative hosts can reach the CLI, with the trade-off of added administrative overhead and possible lockout if ACLs or AAA policies are misconfigured. Restrict local console and SSH access to physically trusted staff and monitor logs for unusual command sequences that precede a sandbox escape; this is detective rather than preventive and will not stop a determined insider, but it shortens dwell time and preserves evidence for incident response.
Affected ProductsAI
The issue affects Arista platforms running EOS releases in which a restricted CLI user role can escape the CLI sandbox to the system shell; the vendor advisory describes the impact as occurring 'on affected platforms', and the definitive list of affected hardware platforms and EOS version ranges is enumerated in Arista Security Advisory 0124 (https://www.arista.com/en/support/advisories-notices/security-advisory/22538-security-advisory-0124). No CPE strings or explicit version ranges were provided in the available intelligence, so the advisory should be treated as the authoritative source for the exact affected-versus-patched release matrix.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Arista EOS exposes a role-based, restricted CLI (the 'sandbox') intended to limit what low-privilege accounts can do, but the underlying operating system is a Linux-based host with full shell access. CVE-2025-54545 is classed as CWE-732 (Incorrect Permission Assignment for Critical Resource): the permission and role assignment separating the restricted CLI from the host shell is insufficient, so a restricted user can pivot through available CLI functionality into a system shell and obtain elevated capabilities. The CVSS vector confirms a local attack path (AV:L) with low complexity (AC:L), low privileges required (PR:L, i.e. an authenticated restricted account), no user interaction (UI:N), and unchanged scope (S:U), while the impact ratings (C:H/I:H/A:H) reflect full control of the device once the breakout succeeds. Note that the source-supplied tag lists this as 'Information Disclosure', which materially understates the assessed high-integrity/high-availability privilege-escalation impact; the authoritative characterization is the vendor-reported privilege escalation documented in Arista Security Advisory 0124.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local CLI access by an authenticated restricted user (PR:L, AV:L), low complexity; breakout to a full system shell yields complete host compromise, so C/I/A all High.
Primary rating from Vendor (arista).
CVSS VectorVendor: arista
DescriptionCVE.org
On affected platforms, a restricted user could break out of the CLI sandbox to the system shell and elevate their privileges.
Executive ViewAI
Arista EOS is affected by CVE-2025-54545, a high-severity local privilege-escalation issue that could let an authenticated, low-privilege CLI user gain full control of the device. For organizations relying on Arista EOS for network operations, exploitation by an insider or an attacker with an existing limited foothold could compromise the device's confidentiality, integrity, and availability, requiring incident response and recovery. No public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis, so leadership should focus on reducing CLI account exposure and readiness to patch quickly.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting and auditing low-privilege CLI accounts on Arista EOS, enforcing least privilege and strong authentication for management access, segmenting management interfaces, and monitoring for sandbox-escape or privilege-escalation activity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB