Description
On affected platforms running Arista EOS with Dynamic Host Configuration Protocol (DHCP) relay configured, an unauthenticated attacker with network access could send a crafted DHCP reply packet from an IP address that is not configured as a helper address, and the relay agent would forward it to clients without validating the source. This could allow the attacker to supply clients with malicious network configuration parameters, potentially resulting in traffic interception or denial of service for affected clients.
Published: 2026-09-15
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Remote network configuration manipulation
Action: Patch Upgrade
AI Analysis

Impact

Arista EOS DHCP relay lacks source-address validation when a relay is enabled. An unauthenticated attacker with network access can forge a DHCP reply packet from an address that is not listed as a helper address. The relay agent forwards this packet to clients, allowing the attacker to deliver malicious network configuration parameters such as incorrect IPs, gateways, or DNS servers. Consequently, clients may experience traffic interception, misrouting, or denial of service.

Affected Systems

The vulnerability affects Arista Networks EOS firmware versions earlier than the release trains containing the patch: EOS 4.36.2F, 4.35.6M, 4.34.8M, and 4.33.10M and later, respectively in each train. Commonly impacted hardware includes the CCS‑720XP, CCS‑710P, CCS‑720DP, CCS‑722XPM, DCS‑7010TX, DCS‑7050CX3, DCS‑7050SX3, CCS‑710XP, CCS‑720DF, CCS‑720DT, CCS‑720XDM, CCS‑720XPM, CCS‑755, CCS‑758, DCS‑7050CX3M, DCS‑7050TX3, DCS‑7304, DCS‑7308, and 7300X3 models that run EOS.

Risk and Exploitability

The CVSS score of 6.5 reflects a moderate severity, while the EPSS score of <1% indicates a very low probability of exploitation at present. The attack vector is network-based and requires only local or sub-net access to transmit crafted DHCP packets. The vulnerability does not demand privileged credentials, but it relies on the existence of a DHCP relay configuration. Although currently low in exploitation likelihood, the impact on client networks is significant if an attacker succeeds. The CVE is not listed in the CISA KEV catalog.

Generated by OpenCVE AI on September 16, 2026 at 21:25 UTC.

Remediation

Vendor Solution

The recommended resolution is to upgrade to a remediated software version at your earliest convenience and enable the reply source-address validation CLI knob under dhcp relay mode: switch(config)# dhcp relay switch(config-dhcp-relay)# reply source-address validation CVE-2026-73437 has been fixed in the following releases: * 4.36.2F and later releases in the 4.36.x train * 4.35.6M and later releases in the 4.35.x train * 4.34.8M and later releases in the 4.34.x train * 4.33.10M and later releases in the 4.33.x train Note: All versions require upgrading to a release containing the fix (as listed above) and applying the required configuration. Arista will not be providing any hotfixes.


Vendor Workaround

IP locking can be run in a locked address enforcement disabled state, along with the DHCP Relay, to provide protection against rogue DHCP servers and spoofing. This is supported on DHCPv4 starting with EOS-4.29.0F and on DHCPv6 starting with EOS-4.27.0F. For more information, see IP Locking https://www.arista.com/en/support/toi/eos-4-25-1f/14628-ip-locking-release-updates . This is compatible with the following platforms only:   * CCS-720XP * CCS-710P * CCS-720DP * CCS-722XPM * DCS-7010TX * DCS-7050CX3 * DCS-7050SX3 * CCS-710XP * CCS-720DF * CCS-720DT * CCS-720XDM * CCS-720XPM * CCS-755 * CCS-758 * DCS-7050CX3M * DCS-7050TX3 * DCS-7304 * DCS-7308 * 7300X3 Untrusted ports can be locked with the following configuration: switch(config)# address locking switch(config-address-locking)# locked-address ipv4 enforcement disabled switch(config-address-locking)# locked-address ipv6 enforcement disabled switch(config)# int et 5 switch(config-if-Et5)# address locking ?   ipv4  Enable address locking for IPv4   ipv6  Enable address locking for IPv6   <cr> switch(config-if-Et5)# address locking ipv4 switch(config-if-Et5)# address locking ipv6   The above configuration can be validated using the following output: switch# show address locking IP Locking is active Logging events: None Bindings persistence is enabled Bindings last backup time: Not Available Configured IPv4 Interfaces:       Et5 Configured IPv6 Interfaces:       Et5 Configured IPv4 VLANs: Configured IPv6 VLANs: Interface Status Interface        IPv4       IPv6 ---------------- ---------- ------------------- Ethernet5        yes*       yes* * Locked address enforcement is disabled   With the above configuration applied, DHCP traffic from untrusted ports can be blocked and the following output reflects the packet drops: switch#show address locking counters detail Action                            Count --------------------------------- ----- ARP (0.0.0.0) PERMIT                  0 DHCP from client to server PERMIT     0 DHCP from server DROP                 4   In releases prior to EOS-4.35.0F, “show address locking counters detail” command is not available. Instead, run “show platform trident tcam detail” and grep for these IP Locking counters. switch#show platform trident tcam detail === TCAM detail for switch Linecard0/0 === Groups programmed in IFP ... TCAM group 129 copy 0 in PIPE 0 uses 3 entries and can use up to 12282 more.   IP Locking v4 uses 3 entries.     0x0000005c            0 hits - Unknown ARP permit rule     0x0000005d            0 hits - DHCP permit from client     0x00000060            4 hits - DHCP drop from server TCAM group 129 copy 1 in PIPE 0 uses 3 entries and can use up to 12282 more.   IP Locking v4 uses 3 entries.     0x0800005c            0 hits - Unknown ARP permit rule     0x0800005d            0 hits - DHCP permit from client     0x08000060            0 hits - DHCP drop from server


OpenCVE Recommended Actions

  • Upgrade the switch to a fixed EOS release (e.g., EOS 4.36.2F or later in the 4.36.x train, or the corresponding fixed release in the 4.35.x, 4.34.x, or 4.33.x trains).
  • Enable reply source-address validation under the dhcp relay CLI mode: "switch(config)# dhcp relay" followed by "switch(config-dhcp-relay)# reply source-address validation".
  • As an interim countermeasure, enable IP locking on untrusted ports with enforcement disabled ("switch(config)# address locking" then "switch(config-address-locking)# locked-address ipv4 enforcement disabled" and verify via "show address locking"), or use the IP locking configuration shown in the Arista work‑around documentation.

Generated by OpenCVE AI on September 16, 2026 at 21:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 16 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 15 Sep 2026 21:30:00 +0000

Type Values Removed Values Added
Description On affected platforms running Arista EOS with Dynamic Host Configuration Protocol (DHCP) relay configured, an unauthenticated attacker with network access could send a crafted DHCP reply packet from an IP address that is not configured as a helper address, and the relay agent would forward it to clients without validating the source. This could allow the attacker to supply clients with malicious network configuration parameters, potentially resulting in traffic interception or denial of service for affected clients.
Title On affected platforms running Arista EOS with Dynamic Host Configuration Protocol (DHCP) relay configured, an unauthenticated attacker with network access could send a crafted DHCP reply packet from an IP address that is not configured as a helper/destinat
Weaknesses CWE-345
References
Metrics cvssV3_1

{'score': 9.6, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}

cvssV4_0

{'score': 6.5, 'vector': 'CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Arista

Published:

Updated: 2026-09-17T03:57:04.541Z

Reserved: 2026-08-12T16:39:35.976Z

Link: CVE-2026-73437

cve-icon Vulnrichment

Updated: 2026-09-16T19:11:37.765Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-15T22:16:58.220

Modified: 2026-09-17T04:17:57.743

Link: CVE-2026-73437

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-16T21:30:06Z

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity