Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network foothold
-
DeliverySend crafted traffic to device
-
ExploitTrigger unauthenticated flaw
-
ExecutionCross scope boundary
-
ImpactCompromise confidentiality/integrity/availability
Vulnerability Assessment
| Exploitation Conditions | Exploitation requires the attacker to be on an adjacent network to the affected HPE networking device (AV:A) - that is, the same Layer-2 segment, VLAN, or logically adjacent broadcast domain rather than the routable internet; this adjacency requirement is the primary limiting factor and means the device is not exploitable by arbitrary remote internet attackers. Within that position, no authentication (PR:N) and no user interaction (UI:N) are needed, and attack complexity is low (AC:L), so once network-adjacent the barrier is minimal. The specific product feature, protocol, or configuration that triggers the flaw is not described in the available sources (no description or CWE was provided), so the concrete prerequisite cannot be named beyond the adjacency requirement. |
| Impact | Signals point to a genuine high-priority issue, but with important caveats. The authoritative CVSS 3.1 vector (AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, base 9.6) describes an adjacent-network, low-complexity, unauthenticated, no-interaction flaw with a scope change and full confidentiality/integrity/availability impact - a severe profile for a networking product. The vuln.today decision label is 'act_now', reinforcing urgency. However, several key signals are MISSING: there is no EPSS score, no CISA KEV listing, and no POC/exploit reference in the input, so exploitation probability cannot be quantified and no active exploitation is confirmed. There is also a conflict between the single tag 'Information Disclosure' (which implies confidentiality-only impact) and the CVSS vector's C:H/I:H/A:H (full triad impact) - verify the true impact with the HPE advisory, as the tag appears to understate the vulnerability. Additionally, no description, CWE, or affected-version/product data was supplied, so the exact mechanism and footprint are unverified. Net assessment: treat as a real priority on the strength of the 9.6 adjacent/unauthenticated vector and the 'act_now' label, while recognizing that the absence of EPSS/KEV/POC means widespread or confirmed exploitation is NOT established - this reads as a high-severity flaw warranting prompt patching rather than evidence of in-the-wild attacks. |
| Exploit ScenarioDerived | An attacker positioned on the same adjacent network segment as the affected HPE networking device (e.g., same LAN/VLAN or broadcast domain) sends crafted traffic to the device without any authentication or user interaction, and because the CVSS scope is changed, the impact extends beyond the vulnerable component to affect confidentiality, integrity, and availability. The precise trigger is not described in the available sources. No public exploit identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
An attacker positioned on an adjacent network can achieve high confidentiality, integrity and availability impact against an affected HPE networking device, reflected in a 9.6 CVSS base score from the vector AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. No authentication and no user interaction are required once the attacker is on the same Layer-2 segment, VLAN or broadcast domain, and the scope-change metric means the compromise can affect resources beyond the vulnerable component itself; the limiting factor is purely the adjacency requirement, so arbitrary internet-side attackers are not in the threat model. No public exploit code has been identified at time of analysis, EPSS and KEV data were not supplied, and the single reference is an HPE support advisory; the vulnerable feature or protocol and the exact trigger are not described in the available sources.
RemediationAI
No vendor-released patch version is identified in the supplied intelligence, so the first action is to retrieve and follow the HPE advisory at https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05162en_us&docLocale=en_US, which carries the authoritative fixed-firmware matrix and any vendor-stated workarounds for the affected product families; apply the listed firmware release to every device the advisory names. Because the assessed vector is AV:A, the exposures that matter most pending a fix are Layer-2 adjacencies to untrusted hosts: tightening segmentation so that the affected devices are not reachable from guest, OT, branch-user or partner VLANs, enforcing port security and 802.1X on access ports, and pruning unnecessary inter-VLAN paths all reduce the set of hosts that can reach the vulnerable surface, at the cost of added network design complexity and possible application breakage where flat L2 reachability is currently assumed. These controls lower the probability of exploitation but do not remove the underlying defect, and the supply chain should plan a maintenance window for the vendor firmware once the fixed version is confirmed from the advisory.
Affected VersionsENISA
Affected Packages
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 root-cause class is unclassified in the supplied data (CWE not assigned), and because no description was published the concrete mechanism - the specific protocol, service, management plane or configuration path on the HPE device that is abused - cannot be named. What is known is the exploitation model encoded in the CVSS vector: AV:A places the attacker on an adjacent network segment rather than the routable internet; AC:L and PR:N/UI:N mean that once that position is obtained the attacker needs no credentials and no victim action; and S:C indicates the resulting impact crosses a trust boundary from the vulnerable component into other resources. High C/I/A impact is notable because the only supplied tag labels the issue as 'Information Disclosure', so the tag likely under-describes the effect relative to the assessed vector - analysts should treat the vector, not the tag, as the impact estimate. The vendor-attributed report (security-alert@hpe.com) and the hpesbnw05162en_us support document indicate this is a networking-device firmware/software issue in HPE's portfolio, but the supplied data does not identify the product line, firmware branch or affected configuration.
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
AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Retaining the HPE-supplied vector: adjacent, unauthenticated, low-complexity with scope change and full impact; impact kept at C:H/I:H/A:H despite the narrower 'Information Disclosure' tag, as no description justifies reducing it.
Primary rating from Vendor (hpe).
CVSS VectorVendor: hpe
DescriptionCVE.org
No description provided
Executive ViewAI
A critical vulnerability (CVE-2026-79871, CVSS 9.6) affects certain HPE networking devices, allowing an unauthenticated attacker on an adjacent network segment to potentially gain full control over confidentiality, integrity, and availability, with scope change that could impact other systems. This places your internal network at risk from anyone who can connect to the same VLAN or broadcast domain, such as a compromised internal host or unauthorized device. Leadership should prioritize immediate network segmentation and patching once available to prevent potential lateral movement and data breaches.
No vendor-released patch identified at time of analysis. Interim mitigations include network segmentation to limit Layer-2 adjacency, restricting access to management interfaces, monitoring for unauthorized devices on VLANs, and applying ACLs to block unnecessary lateral traffic.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
An unprivileged network attacker could gain system privileges to provisioned Intel manageability SKUs: Intel Active Mana
The read_mru_list function in NTP before 4.2.8p9 allows remote attackers to cause a denial of service (crash) via a craf
Default, hard-coded credentials shipped on several administrative and system accounts in HPE's Analytics and Location En
A directory traversal vulnerability in Hewlett Packard Enterprise Insight Remote Support may allow remote code execution
A potential security vulnerability has been identified in Hewlett Packard Enterprise OfficeConnect 1820, 1850, and 1920S
A security vulnerability in HPE Smart Update Manager (SUM) prior to version 8.5.6 could allow remote unauthorized access
A vulnerability in HPE Insight Remote Support (IRS) prior to v7.15.0.646 may allow an unauthenticated denial of service
NTP through 4.2.8p12 has a NULL Pointer Dereference. Rated high severity (CVSS 7.5), this vulnerability is remotely expl
A maximum-severity, network-reachable flaw (CVSS 3.1 base 10.0) in an as-yet-unnamed HPE product allows remote attackers
Unauthenticated network attackers can potentially achieve high confidentiality, integrity, and availability impact again
HPE security bulletin hpesbnw05162en_us documents a maximum-severity (CVSS 10.0) exposure in an HPE product that is not
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
EUVD-2026-108371
GHSA-m7c5-p82v-j7h5
NVD
CVE.org
EPSS
VulDB
Exploit-DB