CVE-2026-120981Arista Networks EOS resource never released
CVE-2026-120981 is a resource never released in Arista Networks EOS, rated medium (6.0 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
Resources are not released after use, so repeated requests exhaust them.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can take it offline. In practice, this kind of flaw lets an attacker exhaust CPU, memory or connections until the service stops answering. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place Arista Networks EOS runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, review who holds accounts that can reach it.
Description from NVD
On affected platforms running Arista EOS with VPLS-BGP enabled, an attacker who has established a BGP session with the PE router can affect the route advertisements of VPLS pseudowires, causing a churn of the established routes with other legitimate BGP peers.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Public entry points and shared services that must stay up. The flaw sits between untrusted traffic and shared capacity.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between untrusted traffic and shared capacity. An attacker who crosses it can exhaust CPU, memory or connections until the service stops answering.
Questions to answer about your own systems
- Where does Arista Networks EOS run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.