CVE-2026-73465

On affected platforms running Arista EOS, under certain circumstances plaintext private keys

Published Sep 15, 2026 CVSS 4.0 · 6 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

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.

Affected Systems

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.

Risk and Exploitability

The CVSS base score is 6, indicating a medium severity risk. The EPSS score is currently less than 1% 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.

Remediation

Vendor Solution

CVE-2026-73465 has been fixed in the following releases: * 4.36.2F and later releases in the 4.36.x train. * 4.35.5M and later releases in the 4.35.x train. * 4.34.8M and later releases in the 4.34.x train. * 4.33.10M and later releases in the 4.33.x train.


Vendor Workaround

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---"


OpenCVE Recommended Actions

  • Upgrade the device to EOS 4.36.2F or later, or 4.35.5M or later, or 4.34.8M or later, or 4.33.10M or later to apply the official fix
  • Follow the CNA workaround by running the provided grep command to search /var/log/agents/ConfigAgent-* for lines containing 'MgmtSecuritySslCertK' and 'PRIVATE KEY' to identify any exposed private keys
  • Disabling the specialized non-standard debugging trace levels prevents the logging of private keys; set the trace level configuration to a standard or minimal level
  • Configure log file permissions and rotate logs promptly to limit the window of exposure and protect existing log entries from unauthorized access

Generated by OpenCVE AI on September 20, 2026 at 13:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Arista
Arista eos
Vendors & Products Arista
Arista eos
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title On affected platforms running Arista EOS, under certain circumstances plaintext private keys
Weaknesses CWE-532
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 6, 'vector': 'CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H'}

Weaknesses
  • CWE-532

    Insertion of Sensitive Information into Log File

Sources

Status
PUBLISHED
Assigner
Arista
Published
Updated
Sep 17, 2026, 11:57 AM
Reserved
Aug 12, 2026, 4:47 PM
Status
Awaiting Analysis
Published
Sep 15, 2026, 7:17 PM
Modified
Sep 17, 2026, 12:18 PM