# CVE-2025-0936: Information disclosure in EOS

> Attackers can obtain remote server credentials logged on local or accounting servers when using gNOI File TransferToRemote on Arista EOS with gNMI enabled.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2025
- **Updated:** 8 May 2025
- **Also known as:** GHSA-gpmf-hwm2-x2mq

## What is CVE-2025-0936?

CVE-2025-0936 is a medium-severity vulnerability in Arista Networks EOS, published on 7 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On affected platforms running Arista EOS with a gNMI transport enabled, running the gNOI File TransferToRemote RPC with credentials for a remote server may cause these remote-server credentials to be logged or accounted on the local EOS device or possibly on other remote accounting servers (i.e. TACACS, RADIUS, etc).

Weakness: CWE-256 (Plaintext Storage of a Password)

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


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

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

## Is CVE-2025-0936 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0936 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0936 is a medium-severity vulnerability in Arista Networks EOS, published on 7 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0936 exists.

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-0936/ (Markdown: https://insights.sbomify.com/CVE-2025-0936/index.md)
```

## Sources

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

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