CVE-2025-54547: Arista Networks DANZ Monitoring Fabric · CWE-613
Affects Arista Networks DANZ Monitoring FabricSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 29 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Arista Networks DANZ Monitoring Fabric | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-54547, European organizations should first audit their use of SSH session multiplexing on Arista DANZ Monitoring Fabric devices and consider disabling multiplexing if it is not essential. Where multiplexing is required, implement strict session management policies including reduced session timeout values and enhanced monitoring of SSH session activity to detect anomalous file operations post-timeout. Network segmentation and access controls should limit SSH access to trusted administrators only. Employ multi-factor authentication and role-based access controls to minimize the risk of privilege misuse. Additionally, maintain up-to-date device firmware and subscribe to Arista security advisories for forthcoming patches addressing this vulnerability. Implement logging and alerting mechanisms to capture unusual SSH session behaviors indicative of exploitation attempts. Finally, conduct regular security training for administrators on secure SSH usage and session management best practices.
Description
On affected platforms, if SSH session multiplexing was configured on the client side, SSH sessions (e.g, scp, sftp) multiplexed onto the same channel could perform file-system operations after a configured session timeout expired