dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-8872

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
On affected platforms running Arista EOS with OSPFv3 configured, a specially crafted packet can cause the OSFPv3 process to have high CPU utilization which may result in the OSFPv3 process being restarted. This may cause disruption in the OSFPv3 routes on the switch. This issue was discovered internally by Arista and is not aware of any malicious uses of this issue in customer networks.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial-of-service vulnerability in Arista EOS OSPFv3 implementation allows specially crafted packets to trigger high CPU utilization in the OSPFv3 process, causing the process to restart and disrupt OSPFv3 routing on affected switches.

MitigationApply Arista EOS patches when available; until then, restrict OSPFv3 packet receipt to trusted neighbors via interface access lists or route-map filters to limit exposure to untrusted packets.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is Arista EOS
    Run 'show version' and verify the vendor is Arista and the OS is EOS
    Affected if Device is not running Arista EOS - not affected
  2. Check EOS software version
    Run 'show version' and note the EOS version number
    Affected if Version matches or precedes the patched release (compare against Arista security advisories)
  3. Verify OSPFv3 is configured
    Run 'show running-config | include ospf' or 'show ipv6 ospf' to check for OSPFv3 configuration
    Affected if No OSPFv3 configuration exists - not affected (vulnerability requires OSPFv3 to be enabled)
  4. Identify interfaces with OSPFv3 enabled
    Run 'show ipv6 ospf interface brief' to list interfaces running OSPFv3
    Affected if No interfaces have OSPFv3 enabled - not affected
  5. Check OSPFv3 process status and CPU usage
    Run 'show processes cpu history' and 'show ipv6 ospf neighbor' to verify OSPFv3 is actively running
    Affected if OSPFv3 process is not running or no neighbors exist - lower risk but version still matters

Affected if running Arista EOS with OSPFv3 enabled on any interface, regardless of version until patched.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Arista EOS patches when available; until then, restrict OSPFv3 packet receipt to trusted neighbors via interface access lists or route-map filters to limit exposure to untrusted packets.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8872 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8872 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data