Skip to main content

HPE NonStop EXPAND CVE-2026-76665

| EUVDEUVD-2026-101826 HIGH
Out-of-bounds Read (CWE-125)
2026-10-15 hpe GHSA-qfg8-xghr-gjxw
7.1
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
  2. Delivery
    Send crafted EXPAND protocol traffic
  3. Exploit
    Trigger out-of-bounds read in EXPAND
  4. Execution
    Leak memory and corrupt process state
  5. Impact
    Disrupt NonStop node availability

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK

1 technique across 1 tactic: Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network adjacency to a NonStop system running the EXPAND networking subsystem - the attacker must be able to reach the EXPAND communication path on the same logical/adjacent network (AV:A), not arbitrary internet access. No authentication is required (PR:N) and no user interaction (UI:N), but high attack complexity (AC:H) means success depends on specific, hard-to-control conditions such as timing/state of the EXPAND process, which significantly limits reliable exploitation. Practical risk is further bounded by the platform's limited deployment footprint and by network segmentation typically placing EXPAND links on controlled internal/interconnect networks.

Impact

This is a moderate-priority issue rather than an urgent one, and the signals are internally consistent but modest. The vendor CVSS vector (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H, base 7.1 HIGH) describes an adjacent-network (AV:A), high-complexity (AC:H), unauthenticated (PR:N) attack with no user interaction, yielding limited confidentiality loss but high integrity and availability impact. No EPSS score, CISA KEV listing, POC, or SSVC decision data was supplied, so there is no evidence of active exploitation or an available exploit - exploitation status is 'no public exploit identified at time of analysis.' The combination of adjacent-only reachability plus high attack complexity materially lowers real-world risk: an attacker must already have a foothold on the same logical network segment as the EXPAND link and win a difficult race/condition-dependent path. One conflict worth flagging: the CWE is CWE-125 (out-of-bounds READ) and the description leads with 'out-of-bounds memory read,' yet the vector asserts I:H/A:H and the text also says 'resulting in buffer overflow' - a pure OOB read does not normally grant high integrity impact, so the integrity rating and the read-vs-write nature should be verified against the HPE advisory (hpesbns05148en_us). Net: a legitimate HIGH to patch on a maintenance cadence, not a drop-everything emergency, given niche deployment, adjacent vector, and high complexity.

Exploit ScenarioDerived

An attacker with access to the same adjacent network as an HPE NonStop system sends specially crafted traffic over the EXPAND networking subsystem to trigger an out-of-bounds memory read. Because attack complexity is high (AC:H), the attacker must satisfy specific timing or state conditions, but success can leak limited memory contents and corrupt/crash the EXPAND process, degrading the fault-tolerant node. No public exploit code is known at the time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
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 15, 2026

Out-of-bounds memory reads in HPE NonStop EXPAND - the networking subsystem of HPE's NonStop fault-tolerant server platform - can expose process memory contents and crash the EXPAND process, giving an adjacent-network attacker both information disclosure and a denial-of-service path. Exploitation requires network adjacency to a NonStop system's EXPAND communication path rather than arbitrary internet reach, no authentication or user interaction is needed, but high attack complexity means success depends on hard-to-control timing and process-state conditions, so reliable exploitation is unlikely. No public exploit code and no confirmed active exploitation have been identified at time of analysis, and the EPSS signal (not provided) is not a driver here; practical risk is further bounded by the platform's narrow deployment footprint and the fact that EXPAND links normally sit on segmented internal or interconnect networks.

RemediationAI

Patch status is not confirmed by the available data - no exact fix version is supplied, so the primary action is to review HPE security bulletin hpesbns05148en_us (https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbns05148en_us&docLocale=en_US) and apply the HPE-provided EXPAND update or superseding NonStop RVU / SPR as directed there; if no patched build is yet published for your release, track the bulletin for the fix announcement rather than assuming the issue is resolved. Until a fix is applied, treat this as a segmentation problem: restrict which hosts can reach the EXPAND communication path on the adjacent network, using firewall or router ACLs and interconnect-level isolation so that only known, trusted NonStop nodes can initiate connections to the affected subsystem - the trade-off is that legitimate cluster and WAN peer traffic must be enumerated carefully or inter-node communication will break. Because the attack vector is adjacency-based rather than internet-facing, ensuring EXPAND links stay off general user VLANs and management networks removes the realistic attack path with minimal operational cost; note that this does not reduce risk from a compromised or malicious insider already resident on the trusted interconnect. Monitor EXPAND process logs and NonStop system event logs for unexpected process terminations or aborts, which are the most likely observable symptom of a triggered out-of-bounds read, and correlate them with any anomalous inbound traffic from peer addresses, since high attack complexity means successful exploitation may appear as sporadic, hard-to-explain process failures rather than a clean alert.

Affected VersionsENISA

HPE NonStop EXPAND T9057L02^AIG and earlier

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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

Technical ContextAI · show details

The root cause is an out-of-bounds read (CWE-125) in the HPE NonStop EXPAND networking subsystem, a component that handles inter-process and inter-node communications across NonStop clusters and WAN links. The affected product is identified by the CPE cpe:2.3:a:hewlett_packard_enterprise:hpe_nonstop_expand:*:*:*:*:*:*:*:*, i.e. an unversioned wildcard indicating the advisory covers the EXPAND product line broadly rather than a single pinned release. An out-of-bounds read occurs when the code indexes past the end of an allocated buffer and returns the adjacent memory to the caller; on a server platform this typically manifests as either memory disclosure into a response or diagnostic path, or as an access violation that terminates the affected process. The vendor vector (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H) and the independent assessment (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H) agree on the adjacent-network attack vector, no privileges required, no user interaction and high complexity, but differ on impact: the independent assessment does not support an integrity impact and rates the consequence as memory/state disruption with high availability impact, which is the more technically plausible outcome of a pure out-of-bounds read. High attack complexity reflects the dependency on specific timing and internal state of the EXPAND process, meaning the bug is not trivially or repeatably triggerable.

Know when Hpe Nonstop Expand 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 7.1 HIGH
AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H
vuln.today AI 5.9 MEDIUM

Adjacent reach and high complexity match EXPAND; an out-of-bounds read (CWE-125) justifies C:L and A:H (crash) but not I:H, so integrity set to N pending vendor confirmation.

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

Primary rating from Vendor (hpe).

CVSS VectorVendor: hpe

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

DescriptionCVE.org

A security vulnerability in HPE NonStop EXPAND may cause out-of-bounds memory read resulting in buffer overflow.

Executive ViewAI

Why It Matters

HPE NonStop EXPAND, the networking subsystem of HPE's fault-tolerant server platform, has an out-of-bounds read vulnerability that can expose process memory and crash the EXPAND process, potentially disrupting critical transaction and communications workloads that depend on NonStop availability. Organizations running HPE NonStop with EXPAND communication paths reachable from adjacent networks are affected, but the practical risk is narrowed by the requirement for network adjacency, high attack complexity, and no public exploit identified at time of analysis. Leadership should prioritize confirming network segmentation and monitoring for anomalous EXPAND behavior while a vendor patch is unavailable.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include strict network segmentation to prevent untrusted adjacent access to EXPAND communication paths, access control lists to allow only trusted hosts, monitoring for anomalous EXPAND crashes or memory disclosure, and engaging HPE support for additional guidance.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Low
niche fault-tolerant platform, mostly finance/telecom core systems
Social Media
1
Sightings
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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
Medium
Technical Impact
Partial

Priority Score

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

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

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