CVE-2025-6979: Arista Edge Threat Management – Arista Next Generation Firewall · Improper Authentication
Affects Arista Edge Threat Management – Arista Next Generation FirewallSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Arista Networks Arista Edge Threat Management - Arista Next Generation Firewall | Affected
| Fixed in– |
AI-suggested
1. Monitor Arista Networks' official channels closely for patches or security advisories addressing CVE-2025-6979 and apply updates immediately upon release. 2. Restrict access to the Captive Portal interface by implementing network-level access controls such as IP whitelisting or VPN-only access to reduce exposure. 3. Employ network segmentation to isolate systems behind the firewall, limiting the potential impact of unauthorized access. 4. Enhance user awareness training to reduce the risk of social engineering or phishing attempts that could facilitate user interaction required for exploitation. 5. Deploy additional authentication mechanisms or multi-factor authentication (MFA) where possible to strengthen access controls beyond the captive portal. 6. Implement continuous monitoring and logging of captive portal access attempts and firewall configuration changes to detect suspicious activity promptly. 7. Consider temporary disabling or limiting captive portal functionality if feasible until a patch is available. 8. Conduct penetration testing and vulnerability assessments focused on captive portal and firewall authentication mechanisms to identify other potential weaknesses. 9. Coordinate with incident response teams to prepare for potential exploitation scenarios and establish rapid containment procedures.
Description
Captive Portal can allow authentication bypass