CVE-2025-54546: Arista Networks DANZ Monitoring Fabric · Incorrect Permissions
Affects Arista Networks DANZ Monitoring FabricSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation 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
Until a vendor patch is released, European organizations should implement strict SSH access controls on DANZ Monitoring Fabric devices, limiting SSH access to trusted administrators only. Disable SSH port forwarding where possible or restrict it through configuration settings or firewall rules. Employ network segmentation to isolate monitoring infrastructure from general user networks, reducing the risk of lateral movement. Monitor SSH sessions for unusual port forwarding activity using logging and anomaly detection tools. Enforce strong authentication mechanisms, such as multi-factor authentication, to reduce the risk of unauthorized access. Regularly audit user privileges on the devices to ensure that only necessary accounts have SSH access. Prepare to deploy vendor patches promptly once available and test updates in controlled environments before production rollout. Additionally, consider deploying intrusion detection systems that can identify suspicious SSH tunneling behavior. Document and rehearse incident response plans specific to network monitoring infrastructure compromise.
Description
On affected platforms, restricted users could use SSH port forwarding to access host-internal services