EUVD-2026-80066

Let me synthesize.

Product: Arista EOS.

Key data: CVSS 4.0 vector: AV:A (adjacent), AC:H, AT:P (attack requirements present), PR:N, UI:N, VC:N, VI:N, VA:H, SC:N, SI:N, SA:H. CVSS score 7.0. CWE-863 (Incorrect Authorization) — hmm, that's a bit odd for a malformed packet handling issue; likely a mismatch worth flagging in confidence notes.

Tags: "Authentication Bypass" — that seems mislabeled; the description is about malformed IS-IS LSP PDU causing graceful restart procedure termination — an availability issue, not auth bypass. Also CWE-863 mismatch. I could emit a data_quality_flag mislabeled_tag "Authentication Bypass". Hmm — is that highly confident? The description says unauthenticated attacker, but it's not authentication bypass — it's a protocol-level denial of service. CWE-863 incorrect authorization. The tag "Authentication Bypass" is arguably wrong. I think it's defensible to flag as mislabeled_tag with medium/high confidence. Let me consider: the rule says only emit flag when input metadata clearly wrong and verifiable. The tag "Authentication Bypass" doesn't match a DoS/availability issue in IS-IS graceful restart. But the CWE is 863 = Incorrect Authorization, which aligns with the tag... though CWE-863 for IS-IS graceful restart is questionable. Hmm. Given the CWE given is 863, the tag isn't clearly wrong relative to provided metadata. I'll be cautious: maybe emit a medium-confidence flag. Actually the guidance says empty array is common and correct. But there's genuine mismatch: description is a malformed packet causing premature termination of graceful restart = availability. No authentication bypass occurs. I'll emit one flag with medium confidence. Hmm, risk of being penalized. I think it's reasonable and defensible... Let me lean toward emitting it since the description clearly describes DoS via malformed packet with no authorization bypass. Actually, tagging "Authentication Bypass" would cause wrong categorization. I'll emit with medium confiden