Skip to main content

HPE Networking Devices EUVDEUVD-2026-108376

| CVE-2026-79876 CRITICAL
2026-10-22 security-alert@hpe.com GHSA-qfwj-hvvq-cfq3
9.3
CVSS 3.1 · Vendor: hpe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain adjacent-network position near HPE device
  2. Exploit
    Send crafted unauthenticated traffic
  3. Impact
    Disclose confidential data and disrupt availability across scope

Vulnerability Assessment

Exploitation Conditions

Exploitation requires the attacker to hold an adjacent-network position (AV:A) - the same local segment / broadcast domain or a logically adjacent network as the affected HPE networking device - rather than arbitrary internet reach; this is the primary limiting factor. Per the CVSS vector the attack is unauthenticated (PR:N) and needs no user interaction (UI:N), with low attack complexity (AC:L). The specific product feature, protocol, or configuration that must be reachable is not described in the available sources (no description was provided), so the concrete trigger condition cannot be named; defenders should treat adjacent-network reachability of the HPE device as the key gating prerequisite.

Impact

Signals are mixed and incomplete. The CVSS 3.1 base score of 9.3 (critical) is driven by an adjacent-network, low-complexity, unauthenticated, no-interaction vector with a changed scope (S:C) and high confidentiality and availability impact (C:H/A:H). Crucially the attack vector is AV:A (Adjacent), not AV:N (Network), so this is not internet-wide mass-exploitable - the attacker must already hold a position on the same logical/adjacent network segment as the affected HPE networking device, which materially narrows realistic exposure versus the raw 9.3 implies. The vuln.today decision label is act_now, which signals vendor/aggregator-assessed urgency and should drive prompt patching. However, EPSS probability is not provided, there is no CISA KEV listing in the input (so no confirmed active exploitation), and no PoC or exploit reference is present, so there is currently no public exploit identified at time of analysis. The most significant limitation is that NO vulnerability description and no CWE were supplied, so the mechanism (what is disclosed, how availability is lost, why scope changes) cannot be verified - the act_now urgency therefore rests on the vendor's own HPE bulletin rather than on independently confirmable exploitation data. Net: treat as a high-priority patch per the act_now label and the critical adjacent-network impact, but recognize the real-world risk is gated by requiring adjacent-network access and that key corroborating signals (EPSS, KEV, description) are absent.

Exploit ScenarioDerived

An attacker already positioned on the same adjacent/local network segment as the affected HPE networking device sends crafted traffic to it without authentication or any user interaction, obtaining confidential information and disrupting availability, with impact extending beyond the vulnerable component due to the changed scope. The precise trigger is not described in the available sources. No public exploit or PoC reference is present in the input.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 22, 2026

HPE networking devices are affected by a CVSS 9.3 flaw that an unauthenticated attacker on an adjacent network can trigger without user interaction, producing high confidentiality and availability impact while integrity impact is rated none; the supplied data does not name the affected feature, protocol, or trigger condition. The independent assessment identifies adjacent-network reachability of the HPE device as the key gating prerequisite, and the vuln.today decision label is act_now. No KEV listing or public exploit reference is present, so no public exploit is identified at time of analysis, and the overall signals remain mixed and incomplete.

RemediationAI

The supplied data does not identify a vendor-released patch, exact fixed version, or vendor workaround; consult the HPE advisory at https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05162en_us&docLocale=en_US for the authoritative patch status and affected product list before planning an upgrade. Because the assessed prerequisite is an adjacent-network position, the directly relevant compensating control is to reduce Layer 2 and Layer 3 reachability to the HPE device from untrusted or unnecessary adjacent segments using network segmentation, ACLs, or firewall policy; the trade-off is added operational complexity and possible disruption of legitimate adjacent management or monitoring traffic, so validate rules against required device communications.

Affected VersionsENISA

Unknown product 10.6.0.0 ≤10.7.2.6
Unknown product 10.8.0.0 ≤10.8.1.1
Unknown product 10.3.0.0 ≤10.4.1.13

Affected Packages

euvd unknown_product no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The supplied CVSS vector is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:H. AV:A means the attacker must be positioned on the same local segment, broadcast domain, or a logically adjacent network rather than reaching the device arbitrarily over the internet; PR:N indicates no authentication is required, UI:N indicates no user interaction, and AC:L indicates low attack complexity. S:C is a scope change, so the impact may extend beyond the vulnerable component, and the confidentiality and availability impacts are both high while integrity impact is none. The CWE is not provided, so the root-cause class is not identifiable from the available data, and the specific product feature, protocol, or configuration that must be reachable is not described in the supplied sources. The reference is an HPE advisory, and the tag is Information Disclosure, which aligns with the high confidentiality rating but does not by itself explain the high availability rating in the assessed vector.

Know when Hpe gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (hpe) PRIMARY 9.3 CRITICAL
AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:H
vuln.today AI 9.3 CRITICAL

No description was provided, so metrics mirror the vendor vector: AV:A reflects a network-device adjacent reach and PR:N/UI:N the unauthenticated bulletin framing; not independently verifiable.

3.1 AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (hpe).

CVSS VectorVendor: hpe

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
High

DescriptionCVE.org

No description provided

Executive ViewAI

Why It Matters

A critical vulnerability in HPE networking devices exposes adjacent-network attackers to potential data theft or service disruption without requiring authentication or user action. Because these devices often sit at the network perimeter or in data centers, successful exploitation could undermine network integrity and availability, requiring immediate leadership attention to assess exposure and implement interim controls.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Enforce strict network segmentation to limit adjacent-network access, monitor network traffic for anomalies, and consider removing affected devices from untrusted segments until a patch is available.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Medium
HPE enterprise networking product; exact model and install base unclear
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Hpe

View all
CVE-2017-5689 CRITICAL POC
9.8 May 02

An unprivileged network attacker could gain system privileges to provisioned Intel manageability SKUs: Intel Active Mana

CVE-2016-7434 HIGH POC
7.5 Jan 13

The read_mru_list function in NTP before 4.2.8p9 allows remote attackers to cause a denial of service (crash) via a craf

CVE-2026-76708 CRITICAL POC
9.8 Sep 22

Default, hard-coded credentials shipped on several administrative and system accounts in HPE's Analytics and Location En

CVE-2024-53676 CRITICAL POC
9.8 Nov 27

A directory traversal vulnerability in Hewlett Packard Enterprise Insight Remote Support may allow remote code execution

CVE-2022-37932 CRITICAL POC
9.8 Dec 12

A potential security vulnerability has been identified in Hewlett Packard Enterprise OfficeConnect 1820, 1850, and 1920S

CVE-2020-7136 CRITICAL POC
9.8 Apr 30

A security vulnerability in HPE Smart Update Manager (SUM) prior to version 8.5.6 could allow remote unauthorized access

CVE-2025-37097 HIGH POC
7.5 Jul 01

A vulnerability in HPE Insight Remote Support (IRS) prior to v7.15.0.646 may allow an unauthenticated denial of service

CVE-2019-8936 HIGH POC
7.5 May 15

NTP through 4.2.8p12 has a NULL Pointer Dereference. Rated high severity (CVSS 7.5), this vulnerability is remotely expl

CVE-2026-79849 CRITICAL
10.0 Oct 22

A maximum-severity, network-reachable flaw (CVSS 3.1 base 10.0) in an as-yet-unnamed HPE product allows remote attackers

CVE-2026-79848 CRITICAL
10.0 Oct 22

Unauthenticated network attackers can potentially achieve high confidentiality, integrity, and availability impact again

CVE-2026-79851 CRITICAL
10.0 Oct 22

HPE security bulletin hpesbnw05162en_us documents a maximum-severity (CVSS 10.0) exposure in an HPE product that is not

CVE-2026-79847 CRITICAL
10.0 Oct 22

HPE advisory hpesbnw05162en_us covers a product flaw carrying a CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy