CVE-2026-73465

Summary

On affected platforms running Arista EOS, under certain circumstances plaintext private keys may be written in clear text to log files during operations when specialized non-standard debugging trace levels are explicitly enabled.

To exploit these vulnerabilities, a malicious actor must already possess authenticated local administrative access to the device shell, and specialized non-standard debugging trace levels must be explicitly enabled.

This issue was discovered internally by Arista, and the company is not aware of any malicious exploitation of this vulnerability in customer networks.

Affected Software

Weaknesses

• CWE-532: CWE-532 Insertion of Sensitive Information into Log File

Workarounds

This vulnerability may lead to exposed private keys on log files. As such, the following messages may appear at /var/log/agents/ConfigAgent-*:

2026-05-07 02:42:18.537932 18813 MgmtSecuritySslCertK 3 validateRsaPrivateKey start: —–BEGIN RSA PRIVATE KEY—–

2026-05-07 02:42:18.537932 18813 MgmtSecuritySslCertK 3 _getPemCount start: —–BEGIN EC PRIVATE KEY—–

These messages can be found with the following grep command, when run from the bash shell:

switch# grep "MgmtSecuritySslCertK" /var/log/agents/ConfigAgent-* | grep "PRIVATE KEY—"

ADP Enrichment

CISA ADP Vulnrichment

• SSVC:
• Exploitation: none
  • Automatable: no
  • Technical Impact: partial

References

• https://www.arista.com/en/support/advisories-notices/security-advisory/24709-security-advisory-0153

• ←Previous
• Next→