Automated Threat Modeling

Quick Look: Arista EOS eAPI Path Traversal (CVE 2026 121371) Allows Unauthenticated Arbitrary File Reads

A brief summary of CVE 2026 121371, an unauthenticated path traversal in the Arista EOS eAPI web service that can expose arbitrary files, including credentials, on switches running default configurations. Covers affected versions, fixed releases, and the vendor mitigation.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Quick Look: Arista EOS eAPI Path Traversal (CVE 2026 121371) Allows Unauthenticated Arbitrary File Reads

Introduction

A path traversal flaw in the eAPI web service of Arista EOS lets an unauthenticated remote attacker read arbitrary files from a switch filesystem, including sensitive credentials. Arista states that the vulnerable conditions (eAPI running with default services enabled on the management HTTP server) reflect default system configurations. That means many EOS switches, virtual instances, and appliances may be exposed without any local configuration change at all.

Arista EOS is the network operating system behind Arista Networks' cloud networking products for data centers and cloud networks. Arista's corporate profile describes customers across cloud, enterprise, financial, and specialty cloud service provider markets, with products delivered worldwide through distribution partners, systems integrators, and resellers. The company's own quick facts page states that it achieved the number one position in the 100, 200, and 400 gigabit ports market in 2020, which is a vendor positioning claim rather than an independent market assessment.

Key facts at a glance:

  • Advisory: Arista Security Advisory 0218, published November 10, 2026
  • Weakness: CWE 22, Improper Limitation of a Pathname to a Restricted Directory (path traversal)
  • Severity: CVSS 3.1 base score 7.5 (High), CVSS 4.0 score 8.7
  • Authentication required: None
  • Exploitation status: No evidence on record of exploitation in the wild, not listed in CISA KEV, and no public exploit code indexed in Metasploit or Exploit DB, according to the Threat Radar page we reviewed

Technical information

What Arista has disclosed

The advisory describes the issue in a single sentence: on affected EOS versions with the eAPI service enabled, a specially crafted HTTP request can allow an unauthenticated, remote attacker to read arbitrary files, including sensitive credentials from the switch filesystem. EOS is closed source, so there is no public commit or diff, and Arista has not published the specific request format, the payload, or the names of files that can be retrieved. We do not attempt to reconstruct an exploit procedure beyond what the advisory supports.

Preconditions

All of the following must hold for a device to be vulnerable:

  1. The device runs an affected EOS release (see the version list below).
  2. eAPI is enabled and running.
  3. Default services are enabled on the management HTTP server. This setting serves the built-in static web content, including the eAPI explorer at /explorer.html and the TapAgg graphical interface.

Arista explicitly warns that these conditions reflect default system configurations. In practice, a device with no local configuration changes is not necessarily safe.

Severity scoring

The CVSS 3.1 scoring Arista assigned breaks down as follows:

  • Attack vector: Network
  • Attack complexity: Low
  • Privileges required: None
  • User interaction: None
  • Confidentiality impact: High
  • Integrity impact: None
  • Availability impact: None

The score reflects a pure information disclosure primitive. The scoring itself assigns no integrity or availability impact. Any downstream consequences would depend on which credentials are exposed and where they are valid, and the advisory does not elaborate on either.

Likely root cause (our inference)

Arista has not described the code change. Three published details, taken together, point at the static file handler behind nginx in the management web server:

  • The weakness is classed as CWE 22.
  • Exploitation requires default services, which is the setting that serves static web content such as the eAPI explorer and the TapAgg GUI.
  • For indicators of compromise, Arista tells operators to look in /var/log/nginx-access.log for irregular HTTP requests "targeting device static resources" that are constructed with "unexpected paths".

Our reading is that the handler serving those static resources did not properly canonicalize request paths or confine them to the web root, so a crafted path could resolve outside that directory and return arbitrary files from the switch filesystem. A fix for this class of bug normally normalizes the requested path, handling traversal sequences and their encoded variants, and rejects anything that resolves outside the allowed directory. Arista has not confirmed any of this.

Attack flow

Based on the advisory and its indicator guidance, exploitation proceeds roughly as follows:

  1. The attacker reaches the management HTTP server hosting eAPI over the network. No credentials or user interaction are needed.
  2. The attacker sends a specially crafted HTTP request aimed at the static resources served under default services, using an unexpected path.
  3. On an affected release, the server resolves that path to a location outside its intended directory and returns the file contents.
  4. The attacker repeats the request for other files of interest, including files holding sensitive credentials on the switch filesystem.

Each such request would be recorded by nginx, which is why Arista directs operators to its access log for review.

Exploitation status

The Threat Radar entry we reviewed reports no evidence on record of exploitation in the wild, states that the CVE is not in the CISA Known Exploited Vulnerabilities catalog, and reports no public exploit code in Metasploit or Exploit DB. It names no threat actor, and its sensor field shows no concrete value, so it can neither confirm nor rule out attack traffic. A CISA KEV alert from November 6, 2026 concerns a different vulnerability and says nothing about this CVE. All of this describes the available records. None of it proves that exploitation has not occurred.

Patch information

Arista shipped the fix in Security Advisory 0218, which is the only patch source NVD lists. Alongside the advisory, Arista publishes a machine-readable CSAF file. Internally the fix is tracked as BUG 2048764 for EOS and BUG 2069205 for DANZ Monitoring Fabric (DMF).

Fixed releases

The fix was delivered inside Arista's normal release trains rather than as a standalone patch:

  • 4.37 train: fixed in 4.37.0F and later
  • 4.36 train: last vulnerable 4.36.3M, fixed in 4.36.3.2M and later
  • 4.35 train: last vulnerable 4.35.7M, fixed in 4.35.7.2M and later
  • 4.34 train: last vulnerable 4.34.9M, fixed in 4.34.9.2M and later
  • 4.33 train: last vulnerable 4.33.11M, fixed in 4.33.11.2M and later
  • 4.32 train and End of Support trains: all releases affected and no fix, so you must move to a supported train

The CSAF file carries the same information in structured form. Each vendor_fix remediation maps to a product ID, for example "Fixed in EOS version 4.36.3.2" and "Fixed in EOS version 4.37.0", while the first affected entry is marked none_available. Vulnerability management tooling that ingests CSAF can match these versions automatically.

Notes on the fix

  1. The fix ships as point releases. On each maintenance (M) train it is a .2 build on top of the last vulnerable version, for example 4.36.3M to 4.36.3.2M and 4.33.11M to 4.33.11.2M, so you can remediate without taking on new features. 4.37.0F is the first feature (F) release that includes the fix from the start.
  2. There is no hotfix. The advisory states: "No hotfix available for this issue." Arista sometimes ships hot patch SWIX extensions for EOS bugs, but not for this one. The only real fix is a full image upgrade, and Arista recommends moving to the latest build on your train rather than the minimum fixed version.
  3. DMF needs its own check. DMF deployments bundle an EOS image for some fabric switches, so they are only remediated once the DMF release bundles a fixed EOS version. Fabric switches running Switch Light OS are not affected.

Applying the fix

First, identify the EOS train on each device:

show version

On a DMF controller, check which EOS image it distributes:

show version details

Then upgrade to at least the first fixed release for that train, ideally the newest build on it, following Arista's EOS upgrade documentation. Devices on 4.32 or an End of Support train need a migration plan to a supported train, since those will never receive a fix.

Temporary mitigation

Until an upgrade is possible, Arista recommends disabling default services on the management HTTP server. This removes access to the built-in eAPI documentation and explorer and to the TapAgg graphical interface, so plan for that operational effect. It is a stopgap, and the upgrade remains the fix. Arista also recommends reviewing /var/log/nginx-access.log for irregular HTTP requests targeting device static resources, especially those constructed with unexpected paths. For further help, Arista directs customers to its Technical Assistance Center via a service request, support email, or regional telephone numbers.

Affected systems and versions

Arista advises checking the software version first: an EOS release not listed as affected is not vulnerable, regardless of hardware platform.

Affected EOS releases

  • 4.36.0F through 4.36.3M
  • 4.35.0F through 4.35.7M
  • 4.34.0F through 4.34.9M
  • 4.33.0F through 4.33.11M
  • 4.32.0F up to but not including 4.33.0F (the entire 4.32 train)
  • Versions before 4.32.0F in the listed legacy range
  • All releases in EOS End of Support trains

Required configuration

  • eAPI enabled and running
  • Default services enabled on the management HTTP server (a default configuration according to Arista)

Affected platforms

EOS-based platforms in the following families:

  • 710, 720, 750, 7010, 7020, 7130, 7170, 7050, 7060, 7260, 7280, 7300, 7320, 7358, 7368, 7388, 7500, 7700, and 7800 series
  • AWE 5000 and 7200R
  • ZTX 7200
  • CloudEOS
  • cEOS lab and vEOS lab
  • CloudVision eXchange appliances

DANZ Monitoring Fabric

Managed fabric switches may be impacted when the EOS version bundled with a DMF release falls within the affected range. The following are not affected:

  • Switches running Switch Light OS
  • DMF Controller, Analytics Node, Recorder Node, and Service Node appliances

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization