# CVE-2025-3456: Information disclosure in EOS

> Attackers with log access can retrieve clear-text encryption keys from Arista EOS accounting logs to decrypt neighbor protocol secrets.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2025
- **Updated:** 12 Oct 2026
- **Also known as:** GHSA-qx5m-jj5c-5j9v

## What is CVE-2025-3456?

CVE-2025-3456 is a low-severity vulnerability in Arista Networks EOS, published on 25 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On affected platforms running Arista EOS, the global common encryption key configuration may be logged in clear text, in local or remote accounting logs. Knowledge of both the encryption key and protocol specific encrypted secrets from the device running-config could then be used to obtain protocol specific passwords in cases where symmetric passwords are required between devices with neighbor protocol relationships.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-3456?


## How do I fix CVE-2025-3456?

No fix has been published for CVE-2025-3456 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3456 being exploited?

There is no known exploitation of CVE-2025-3456 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3456 and fix it if it is affected.

What it is: CVE-2025-3456 is a low-severity vulnerability in Arista Networks EOS, published on 25 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3456 in the wild and no public exploit code.

Affected product: Arista Networks EOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3456/ (Markdown: https://insights.sbomify.com/CVE-2025-3456/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3456
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3456
- OSV: https://osv.dev/vulnerability/CVE-2025-3456

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3456/
Summaries are generated and may contain mistakes; the official description above is the record.