Skip to main content

HPE Networking CVE-2026-79869

| EUVDEUVD-2026-108369 CRITICAL
2026-10-22 security-alert@hpe.com GHSA-pq96-5wq3-j4gr
9.6
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 access to device
  2. Delivery
    Send crafted unauthenticated traffic
  3. Exploit
    Exploit low-complexity flaw
  4. Execution
    Cross security boundary (scope change)
  5. Impact
    Compromise confidentiality, integrity and availability

Vulnerability Assessment

Exploitation Conditions

Exploitation requires the attacker to have Adjacent network access (AV:A) - i.e. presence on the same local/logical network segment (such as a shared VLAN, broadcast domain, or directly attached link) as the affected HPE networking device; it is NOT reachable from the open internet without first obtaining that adjacency. Within that position, no authentication (PR:N) and no user interaction (UI:N) are needed and attack complexity is low (AC:L). The specific product feature, protocol, or configuration mode that triggers the flaw is not described in the available sources (no description or CWE provided). The primary limiting factor is therefore the adjacency requirement, which confines realistic attackers to those with local network foothold or physical/adjacent proximity.

Impact

The CVSS 3.1 base score of 9.6 (Critical) is driven by an unauthenticated (PR:N), low-complexity (AC:L), no-interaction (UI:N) vector with a scope change (S:C) and full confidentiality, integrity and availability impact (C:H/I:H/A:H). Crucially the attack vector is Adjacent (AV:A), NOT Network - exploitation requires the attacker to already be on the same logical/physical adjacent network segment as the affected HPE networking device, so this is not directly internet-reachable and the real-world blast radius is narrower than a comparable AV:N 9.6 flaw. The vuln.today decision label is 'act_now', signalling high remediation urgency, yet no KEV listing, EPSS probability, or PoC/exploit reference was supplied, so there is no public exploit identified at time of analysis and no evidence of active or at-scale exploitation - the urgency appears to rest on severity and vendor advisory rather than observed in-the-wild activity. Two signals should be verified before treating this as confirmed fact: there is NO vulnerability description and NO CWE, so the mechanism is unknown; and the single tag 'Information Disclosure' conflicts with the supplied vector's I:H/A:H (integrity/availability impact), which implies more than disclosure - verify the actual impact and trigger with HPE bulletin hpesbnw05162en_us.

Exploit ScenarioDerived

An attacker positioned on the same adjacent network segment as a vulnerable HPE networking device (e.g. a connected management or client VLAN) sends crafted traffic to the device without any authentication or user interaction. Because the scope changes (S:C), successful exploitation lets the attacker impact resources beyond the vulnerable component itself, potentially compromising confidentiality, integrity and availability across a security boundary. No public exploit code or PoC reference was provided, and the exact trigger is not described in the available sources.

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

High-impact compromise of affected HPE networking devices is possible for unauthenticated attackers who obtain adjacent-network access in CVE-2026-79869 (CVSS 9.6). The assessed vector is AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, so no credentials or user interaction are needed once the attacker is on the same local or logical network segment, and the scope change plus full confidentiality, integrity and availability impact make this an act_now priority. No public exploit is identified at time of analysis, and the provided sources do not describe the product-specific trigger.

RemediationAI

No vendor-released patch or exact fixed firmware version is identified in the provided data; check the HPE advisory at https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05162en_us&docLocale=en_US for the fixed release and affected model list, and treat this as act_now per the vuln.today decision label. Until a fixed firmware is available or confirmed, reduce exposure by enforcing the adjacency precondition: place affected HPE devices behind strict VLAN segmentation and ACLs so only trusted local segments can reach them, and monitor for unauthorized layer-2 adjacency. Trade-off: VLAN and ACL changes can disrupt legitimate management or network traffic and require change control.

Affected VersionsENISA

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

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

CVE-2026-79869 affects HPE networking devices, but the provided data gives no model, firmware version, CPE, CWE, or feature-level detail. The CVSS 3.1 vector AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H describes an unauthenticated, low-complexity attack launched from an adjacent-network position, with no user interaction, a scope change, and high impact on confidentiality, integrity and availability. The Information Disclosure tag is the only vulnerability-class hint; it does not identify the protocol, service, or configuration mode that triggers the flaw, and the trigger is not described in the available sources. Adjacency, such as presence on a shared VLAN, broadcast domain, or directly attached link, is the main precondition.

Know when the next one hits your stack

  • 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.6 CRITICAL
AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.6 CRITICAL

Adopts the supplied vector: AV:A (adjacent-only networking device), AC:L and PR:N/UI:N (unauthenticated, no interaction), S:C with full triad impact; no description exists to justify downgrading any metric.

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

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
High
Availability
High

DescriptionCVE.org

No description provided

Executive ViewAI

Why It Matters

CVE-2026-79869 is a critical (CVSS 9.6) vulnerability in HPE networking devices that can be fully compromised by an unauthenticated attacker who gains access to an adjacent network segment. Because exploitation requires no credentials or user interaction and yields complete loss of confidentiality, integrity and availability across the device and beyond (scope change), any organization relying on these HPE devices for its network backbone faces potential broad operational disruption. Leadership should care because a compromise at this layer can cascade to dependent business services, expose sensitive data, and disable connectivity organization-wide.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: enforce strict network segmentation and ACLs to prevent unauthenticated adjacent-network access, restrict management access to dedicated out-of-band networks, enable enhanced logging and monitoring for anomalous traffic, and apply vendor-recommended hardening and workarounds pending a fix.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
HPE networking bulletin (hpesbnw); enterprise gear common but exact product unconfirmed
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
Very High

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +48
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.

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