Security Advisory 0175

Answer in brief

CVE-2026-73468 records a Unknown severity vulnerability in Security Advisory 0175. 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 Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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	>=1.0.0 <4.33.0F \|\| 4.33.0F \|\| 4.34.0F \|\| 4.35.0F \|\| 4.36.0F	4.33.0F

Recommended response

Check inventory. Check lockfiles and deployed manifests for Arista Networks/EOS.
Review the reported fix. Update Arista Networks/EOS to 4.33.0F if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

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

Sources and claim methodology

Source referencearista.com

Upstream source description

A specially crafted packet can cause the premature expiry of multicast forwarding state on affected interfaces, potentially resulting in temporary multicast traffic loss during the affected period.

Quoted source text, attributed separately from HOL analysis.