Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain position on adjacent network segment
-
DeliverySend crafted traffic to HPE device
-
ExploitTrigger unauthenticated low-complexity flaw
-
ExecutionAchieve full CIA compromise
-
ImpactPivot to resources beyond vulnerable component (scope change)
Vulnerability Assessment
| Exploitation Conditions | Exploitation requires the attacker to be on the same adjacent/local network segment as the affected HPE networking device (AV:A) - e.g., an attacker who has already breached the LAN/VLAN or is otherwise logically adjacent; it is NOT reachable as a straightforward internet-facing remote attack without such a foothold. No authentication and no user interaction are required (PR:N, UI:N) and attack complexity is low (AC:L), so once adjacency is achieved there are no further confirmed prerequisites. The adjacent-network requirement is the primary limiting factor reducing realistic exposure. Because no description or CWE is provided, the exact triggering feature, protocol, configuration setting or deployment mode is not described in the available sources and should be confirmed against HPE bulletin hpesbnw05162en_us. |
| Impact | Signals are mixed and some are absent. The CVSS 3.1 vector (AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, base 9.6 Critical) describes an unauthenticated, low-complexity attack with no user interaction and a scope change yielding full confidentiality, integrity and availability impact - severe on its own terms. The critical mitigating metric is AV:A (Adjacent), meaning the attacker must already hold a position on the same local/adjacent network segment rather than exploiting across the open internet, which materially narrows the realistic attacker set versus a true AV:N remote flaw. The vuln.today decision label is act_now, so this should be treated as high urgency despite the following gaps: no EPSS score, no CWE, no CISA KEV listing, and no PoC or exploit reference are present in the input, so there is no public evidence of active exploitation or available exploit code. There is also a conflict to flag: the sole tag is 'Information Disclosure', but the CVSS vector asserts high integrity AND availability impact plus a scope change - the impact profile is broader than information disclosure alone, so the tag understates the vulnerability; verify the true impact against the HPE bulletin. Net: a genuinely critical-severity flaw whose real-world priority is driven by the act_now label and critical CVSS, but tempered by the adjacent-network precondition and the absence of any exploitation evidence - prioritize patching of exposed/adjacent-reachable HPE networking devices while recognizing this is not confirmed as mass-exploited. |
| Exploit ScenarioDerived | An unauthenticated attacker who has already gained a foothold on the same adjacent network segment as a vulnerable HPE networking device sends crafted traffic to it; because the flaw requires no privileges, no user interaction and is low-complexity, the attacker achieves high confidentiality, integrity and availability impact, and the scope change (S:C) implies impact beyond the vulnerable component itself. No public exploit code or PoC reference is present in the input at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
HPE networking devices carry a CVSS 9.6 flaw that an unauthenticated attacker on the same adjacent or local network segment can use without user interaction; the changed-scope vector (S:C) indicates the impact can cross a security boundary, with high confidentiality, integrity and availability consequences. The affected models, firmware branches and the exact protocol or feature involved are not described in the available sources, so scope must be confirmed against HPE bulletin hpesbnw05162en_us, which is the only reference supplied. Exploitation has not been publicly demonstrated: no public exploit code and no CISA KEV listing was provided, and no EPSS score was supplied, although the vuln.today priority label is act_now, so the exposure should be treated as requiring prompt action pending vendor details.
RemediationAI
No vendor-released patch version is identified in the available data; the only authoritative source supplied is HPE bulletin hpesbnw05162en_us at https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05162en_us&docLocale=en_US, which must be consulted for the fixed firmware releases per affected platform and for any vendor-stated workarounds, since HPE has not published remediation details through this feed. Pending that, the practical lever derives directly from the assessed AV:A vector: reduce adjacency by enforcing strict segmentation between user, guest and IoT VLANs and management/infrastructure segments, applying ACLs on management interfaces, and using 802.1X or MAC-based port authentication on access ports - the trade-off is added network complexity and possible disruption to legitimate cross-segment management traffic, so stage ACL and segmentation changes carefully. Ensure any management or diagnostics services on the devices are not reachable from shared segments, accepting that this may restrict monitoring and administrative tooling. Validate the actual affected models, firmware branches and trigger conditions against the HPE bulletin rather than assuming universal impact across the HPE networking range, as no CPE or version data was provided here.
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 assessed vector is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. AV:A means the attacker must already sit on the same adjacent or local network segment as the device - a breached LAN/VLAN or a logically adjacent position - rather than reaching it directly from the internet; AC:L, PR:N and UI:N mean that once that adjacency exists, no authentication or user interaction is needed and there are no further confirmed prerequisites. S:C (scope changed) means the exploited component can affect resources beyond its own security authority, which is why the vector's impact ratings are all High. No CWE was supplied, so the root-cause class is unknown, and the trigger - the specific protocol, feature, configuration setting or deployment mode - is not described in the available sources. The supplied tag categorises the issue as Information Disclosure, which is narrower than the vector's high integrity and availability impact; that discrepancy, together with the absence of CPE data, means the affected product matrix and true impact profile should be verified against HPE bulletin hpesbnw05162en_us before relying on either the tag or the full impact ratings.
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
AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Adopts the supplied vector as no description contradicts it: AV:A for the adjacent-network precondition, PR:N/UI:N/AC:L per source, with S:C and C/I/A:H reflecting the stated full impact.
Primary rating from Vendor (hpe).
CVSS VectorVendor: hpe
DescriptionCVE.org
No description provided
Executive ViewAI
A critical vulnerability in HPE networking devices (CVSS 9.6) allows unauthenticated attackers on the same network segment to compromise confidentiality, integrity, and availability, potentially crossing security boundaries. Leadership should prioritize this because network infrastructure is foundational, and exploitation could disrupt operations or expose sensitive data.
No vendor-released patch identified at time of analysis. Interim mitigations include network segmentation to limit attacker access, restricting management interface access to trusted hosts, monitoring for exploitation attempts, and applying any vendor-recommended configuration changes from the advisory.
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.
EUVD-2026-108366
GHSA-mrc3-qq5w-rw79
NVD
CVE.org
EPSS
VulDB
Exploit-DB