High · CVSS 8.7CVE-2026-120982

Security Advisory 0207CVE-2026-120982

Answer in brief

CVE-2026-120982 records a High severity (CVSS 8.7) vulnerability in Security Advisory 0207. The current sources do not mark it as known exploited. The current feed maps Arista Networks/EOS (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Nov 10, 2026Updated Nov 10, 2026Source checked Nov 10, 2026First seen by HOL Nov 10, 2026Material review Nov 10, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.7
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Arista Networks/EOS (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Arista Networks/EOSgeneric	>=4.36.0F <=4.36.2F \|\| >=4.35.0F <=4.35.6M \|\| >=4.34.0F <=4.34.8M \|\| >=4.33.0F <=4.33.10M \|\| >=1.0.0 <4.33.0F	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Arista Networks/EOS.
Review the reported fix. Source-reported workaround: router bgp <asn> neighbor default received attribute discard 22 The above configuration applies the mitigation globally. The attribute can be re-enabled on specific peers if it is required within the customer application. For example: router bgp <asn> no neighbor X.X.X.X received attribute discard 22 Alternatively, a recommended mitigation to reduce exposure to this vulnerability is to configure BGP peer authentication using TCP-AO in order to ensure that only authorized peers can establish a BGP session.

Evidence timeline and material changes

Published upstream
Nov 10, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Nov 10, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Nov 10, 2026

Sources and claim methodology

Source referencearista.com

Upstream source description

On affected platforms running Arista EOS with Border Gateway Protocol (BGP) configured, An unauthenticated attacker who can establish a BGP peering session with an affected device and can send specially crafted BGP messages to cause repeated BGP session resets, enabling sustained disruption to network routing and traffic forwarding.

Quoted source text, attributed separately from HOL analysis.

Affected scope and exposure questions

The current feed maps Arista Networks/EOS (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Arista Networks/EOSgeneric	>=4.36.0F <=4.36.2F \|\| >=4.35.0F <=4.35.6M \|\| >=4.34.0F <=4.34.8M \|\| >=4.33.0F <=4.33.10M \|\| >=1.0.0 <4.33.0F	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Arista Networks/EOS.

Review the reported fix. Source-reported workaround: router bgp <asn> neighbor default received attribute discard 22 The above configuration applies the mitigation globally. The attribute can be re-enabled on specific peers if it is required within the customer application. For example: router bgp <asn> no neighbor X.X.X.X received attribute discard 22 Alternatively, a recommended mitigation to reduce exposure to this vulnerability is to configure BGP peer authentication using TCP-AO in order to ensure that only authorized peers can establish a BGP session.

Sources and claim methodology

Upstream source description

Quoted source text, attributed separately from HOL analysis.