Skip to main content
CVE-2025-6978VulnerabilityPublished

CVE-2025-6978: Arista Edge Threat Management – Arista Next Generation Firewall · OS Command Injection

Affects Arista Edge Threat Management – Arista Next Generation FirewallSource CVE Database V5

0

Not known to be exploited · 13% EPSS · CVSS 7.2 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
13.4% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Arista Networks Arista Edge Threat Management - Arista Next Generation FirewallAffected
  • =0.0
Fixed in–

AI-suggested

1. Implement strict access controls to limit administrative and diagnostic command access to trusted personnel only. 2. Monitor and audit usage of diagnostic commands for unusual or unauthorized activity. 3. Employ network segmentation to isolate management interfaces of Arista firewalls from general network access. 4. Use multi-factor authentication (MFA) for all privileged accounts to reduce risk of credential compromise. 5. Apply principle of least privilege to restrict user permissions and reduce potential attack vectors. 6. Stay informed on Arista's security advisories and apply patches immediately once released. 7. Consider deploying intrusion detection/prevention systems (IDS/IPS) to detect anomalous command injection attempts. 8. Conduct regular vulnerability assessments and penetration testing focused on firewall management interfaces. 9. Develop incident response plans specific to firewall compromise scenarios to minimize impact if exploited.

Description

Diagnostics command injection vulnerability

References

Community reviews

Loading reviews…