CVE-2025-1259On affected platforms running Arista EOS with OpenConfig configured, a gNOI request can be run when it should have been rejected.
- 7.7HighCVSS base score
- 0.35%Exploitation in 30 daysEPSS · top 71% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
On affected platforms running Arista EOS with OpenConfig configured, a gNOI request can be run when it should have been rejected. This issue can result in users retrieving data that should not have been available
Timeline
ID reserved
By Arista
- 20 days later
· 20 days later
Published
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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| AristaCNA (assigner) | 3.1 | High7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| NVDNVD · Deferred | 3.1 | High7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
- EPSS (exploitation in 30 days)
- 0.35% · top 71% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.7.
Affected products
- affected 4.33.0 – ≤ 4.33.1
- affected 4.32.0 – ≤ 4.32.3
- affected 4.31.0 – ≤ 4.31.5
- affected 4.30.0 – ≤ 4.30.8
- affected 4.29.0 – ≤ 4.29.9
- affected 4.28.0 – ≤ 4.28.12
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-1259 is fixed in the following releases: * 4.33.2 and later releases in the 4.33.x train * 4.32.4 and later releases in the 4.32.x train * 4.31.6 and later releases in the 4.31.x train * 4.30.9 and later releases in the 4.30.x train * 4.29.10 and later releases in the 4.29.x train * 4.28.13 and later releases in the 4.28.x train
Workaround: For releases with gNSI Authz (EOS 4.31.0F and later releases), the gNOI RPC’s 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 (config-mgmt-api-gnsi)#transport gnmi [NAME] Where [NAME] is the name of the running gNMI transport which gNSI will run on. 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. Note this will replace any existing authz policies located at /persist/sys/gnsi/authz/policy.json For CVE-2025-1259 the following CLI command (highlighted in yellow following the switch prompt) can be run which will disable all gNOI Get RPC’s. switch#bash timeout 100 echo "{\"name\":\"block gNOI GET RPC's policy\",\"allow_rules\":[{\"name\":\"allow_all\"}],\"deny_rules\":[{\"name\":\"no-gnoi-get\",\"request\":{\"paths\":[\"/gnoi.packet_link_qualification.LinkQualification/List\",\"/gnoi.certificate.CertificateManagement/GetCertificates\",\"/gnoi.os.OS/Verify\",\"/gnoi.healthz.Healthz/Get\",\"/gnoi.healthz.Healthz/List\",\"/gnoi.system.System/RebootStatus\",\"/gnmi.gNMI/Subscribe\",\"/gnoi.file.File/Stat\",\"/gnoi.system.System/Traceroute\",\"/gnoi.packet_link_qualification.LinkQualification/Get\",\"/gnoi.system.System/Ping\",\"/gnoi.file.File/Get\",\"/gnsi.authz.v1.Authz/Probe\",\"/gnsi.credentialz.v1.Credentialz/GetPublicKeys\",\"/gnsi.pathz.v1.Pathz/Probe\",\"/gnoi.healthz.Healthz/Acknowledge\",\"/gnsi.certz.v1.Certz/CanGenerateCSR\",\"/gnmi.gNMI/Get\",\"/gnoi.certificate.CertificateManagement/CanGenerateCSR\",\"/gnoi.healthz.Healthz/Artifact\",\"/gnsi.authz.v1.Authz/Get\",\"/gnoi.system.System/Time\",\"/gnsi.pathz.v1.Pathz/Get\",\"/gnoi.packet_link_qualification.LinkQualification/Capabilities\",\"/gnsi.acctz.v1.AcctzStream/RecordSubscribe\",\"/gnsi.credentialz.v1.Credentialz/CanGenerateKey\",\"/gnoi.healthz.Healthz/Check\",\"/gnsi.certz.v1.Certz/GetProfileList\"]}}]}" | sudo tee /persist/sys/gnsi/authz/policy.json && sleep 11
References
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-7379 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-1259)Record last updated .