Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-0936On 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

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).

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. A reference of the record is tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.

Show the exploits1

Timeline

  1. ID reserved

    By Arista

  2. · 3 months later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-0936, by who scored it
Scored byCVSSScoreVector
AristaCNA (assigner)3.1Medium6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVDNVD · Deferred3.1Medium6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS (exploitation in 30 days)
0.29% · top 78% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.

Affected products

  • Arista Networks · EOS

    • affected 4.33.0 – ≤ 4.33.1
    • affected 4.32.0 – ≤ 4.32.3M
    • affected 4.31.0 – ≤ 4.31.5M
    • affected 4.30.1F – ≤ 4.30.9M

What to do

Solution: The recommended resolution is to upgrade to a remediated software version at your earliest convenience. Arista recommends customers move to the latest version of each release that contains all the fixes listed below. For more information about upgrading see EOS User Manual: Upgrades and Downgrades https://www.arista.com/en/um-eos/eos-upgrades-and-downgrades CVE-2025-0936 has been fixed in the following releases: * 4.30.10M and later releases in the 4.30.x train * 4.31.7M and later releases in the 4.31.x train * 4.32.5M and later releases in the 4.32.x train * 4.33.2F and later releases

Workaround: There are a number of possible workarounds: Option 1 - disable accounting/logging for the OpenConfig transportFor example to disable accounting for transport named “default”: switch(config)#management api gnmi switch(config-mgmt-api-gnmi)#transport grpc default switch(config-gnmi-transport-default)#no accounting requests   to disable logging for the OpenConfig agent, run: switch(config)#no trace OpenConfig setting   Option 2 - disable the gNOI File service entirelyTo disable the gNOI File service, override the OCGNOIFileToggle, then restart OpenConfig to load the changes switch#bash timeout 100 echo "OCGNOIFileToggle=0" >> /mnt/flash/toggle_override switch#agent OpenConfig terminate   Disabling the gNOI File service will mean that gNOI clients will no longer be able to call any gNOI File RPCs Option 3 - block the TransferToRemote RPC using gNSI AuthzFor releases with gNSI Authz (EOS 4.31.0F and later releases), the TransferToRemote RPC can be blocked using gNSI Authz. First enable gNSI Authz service by adding the following config: switch(config)#management api gnsi switch(config-mgmt-api-gnsi)#service authz Where [NAME] is the name of the running gNMI transport Adding this config will cause the named gNMI transport to reload. Next update the authz policy to block access to the TransferToRemote RPC. This can be done directly on the system by updating the Authz policy file and waiting at least 10 seconds for OpenConfig to reload the changes: switch#bash timeout 100 echo "{\"name\":\"block gNOI TransferToRemote policy\",\"allow_rules\":[{\"name\":\"allow_all\"}],\"deny_rules\":[{\"name\":\"no-one-can-use-gnoi-transfer-to-remote\",\"request\":{\"paths\":[\"/gnoi.file.File/TransferToRemote\"]}}]}" | sudo tee /persist/sys/gnsi/authz/policy.json && sleep 11   This will cause attempts to run the TransferToRemote RPC to fail with a “PermissionDenied” error code.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-0936 badge
[![CVE-2025-0936](https://cveledger.app/badge/CVE-2025-0936.svg)](https://cveledger.app/cve/CVE-2025-0936)

Record last updated .