The vulnerability causes Arista EOS devices to write plaintext RSA or EC private keys to log files when certain non‑standard debugging trace levels are explicitly enabled. The affected code directly logs the key material, potentially allowing anyone who can read the logs to obtain the private keys. This grants the attacker full access to cryptographic credentials and undermines the confidentiality and integrity of network communications.

Arista Networks EOS systems that have not yet jumped to the fixed releases—4.36.2F or later in the 4.36.x train, 4.35.5M or later in the 4.35.x train, 4.34.8M or later in the 4.34.x train, and 4.33.10M or later in the 4.33.x train—expose private keys when specialized non‑standard debugging trace levels are explicitly enabled, so any device running an earlier train is at risk.

The CVSS v3 base score is 6.0, indicating a medium severity risk. The EPSS score is currently not available, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires that an attacker already has authenticated local administrative access to the device shell and must manually enable the specialized debugging trace levels. While the conditions are restrictive, a compromised local account combined with enabled traces could result in permanent private key exposure through log files.