Skip to main content

HPE NonStop CIPSAM EUVDEUVD-2026-101811

| CVE-2026-76660 HIGH
Improper Input Validation (CWE-20)
2026-10-15 hpe GHSA-hg3w-64g2-5pvm
8.7
CVSS 3.1 · Vendor: hpe
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privileged local/application access
  2. Delivery
    Submit crafted malformed input to CIPSAM
  3. Exploit
    Trigger out-of-bounds write
  4. Execution
    Corrupt buffer and cross privilege boundary
  5. Impact
    Compromise integrity/availability of affected services

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Exploitation requires LOCAL access to an HPE NonStop system running the CIPSAM component at version T0693L02^BAU or earlier (AV:L), plus at least low-level privileges or an authenticated foothold (PR:L) - it is NOT remotely exploitable by an unauthenticated attacker. The attacker must be able to deliver malformed/crafted input to CIPSAM to trigger the out-of-bounds write; no end-user interaction is needed (UI:N) and attack complexity is low (AC:L). Limiting factors: the requirement for prior local access and credentials on a proprietary, access-controlled mission-critical platform significantly narrows the realistic attacker population compared to the raw 8.7 score. The description does not name a specific non-default configuration toggle, so the condition is the presence of a vulnerable CIPSAM version plus local privileged reachability.

Impact

The CVSS 3.1 base score of 8.7 (vector AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H) is driven not by remote reach but by a changed scope combined with High integrity and availability impact - the attack vector is explicitly LOCAL and requires at least low-level privileges (PR:L), so this is an authenticated, local-access issue rather than a remotely-wormable one. No EPSS probability, CISA KEV entry, or public POC is present in the supplied intelligence, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The signals are internally consistent (local vector + required privileges + no exploitation data), so this is best treated as a credible but NOT top-tier, internet-facing emergency: the high score reflects potential impact on a mission-critical platform once an attacker already has a foothold, not ease of initial access. Key caveat: the description is sparse (only 'out-of-bounds write that can corrupt buffer data') and does not confirm whether the integrity/availability impact equates to code execution or merely data/service corruption - verify exploitability details with the HPE advisory (hpesbns05148en_us). Prioritize patching on NonStop systems where untrusted or lower-privileged users have local/application access, but it does not demand the same emergency response as an unauthenticated network RCE.

Exploit ScenarioDerived

An attacker who already holds a low-privileged account or application-level access on an HPE NonStop system supplies malformed input to the CIPSAM component, triggering an out-of-bounds write that corrupts buffer data. Because the CVSS scope is changed with High integrity and availability impact, successful corruption could affect components beyond CIPSAM's own privilege boundary, potentially crashing or manipulating dependent services. No public exploit code is available, so exploitation currently requires original research against a proprietary, niche platform.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 15, 2026

An out-of-bounds write in HPE NonStop CIPSAM (version T0693L02^BAU and earlier) lets an attacker with local access and at least low-level privileges corrupt adjacent buffer memory, producing High integrity and High availability impact on the affected NonStop system. The CVSS 3.1 base score of 8.7 is driven by the changed-scope metric combined with those impact values rather than by remote reach - the vector is AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H, so this is an authenticated, local-access issue and is not remotely exploitable by an unauthenticated attacker. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the realistic attacker population is narrowed by the requirement for prior credentials on a proprietary, access-controlled mission-critical platform.

RemediationAI

No vendor-released patch version is identified in the available data, so the first action is to consult the HPE security bulletin at https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbns05148en_us&docLocale=en_US to obtain the exact fixed CIPSAM build and apply it to any system running T0693L02^BAU or earlier; treat that bulletin as the source of truth for the correct upgrade path rather than assuming a version number. Until the fixed build is installed, the most effective compensating control is to restrict local logon and command access to the NonStop system and to the CIPSAM interface so that only the smallest possible set of trusted, vetted operators holds the low-level privileges needed to reach the component (the flaw requires PR:L, so reducing the number of accounts that satisfy that prerequisite directly shrinks the attack surface) - the trade-off is operational friction and slower break-fix for legitimate administrators. Where CIPSAM accepts external or batch input, validate and constrain the shape and length of data passed to it at the calling layer and reject malformed records before they reach the component, accepting that this is a partial mitigation and will not cover every code path. Apply least-privilege and separation of duties to NonStop user IDs, disable or remove unused accounts and any interactive shell access for service identities, and audit for anomalous CIPSAM process aborts, trap dumps, or memory corruption indicators that would signal an attempted or successful trigger. Because exploitation is local and authenticated, prioritize network and console-access hardening over perimeter controls, and note that no public exploit code has been identified, so the immediate urgency is driven by the high integrity/availability impact and changed scope rather than by known active attacks.

Affected VersionsENISA

HPE NonStop CIPSAM T0693L02^BAU 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

CIPSAM is a component of the HPE NonStop server software stack reached through the local execution environment; the available advisory data does not expand the acronym, so the precise subsystem role should be confirmed against the HPE security bulletin. The flaw is classified under CWE-20 (Improper Input Validation), which is a broad parent category that in practice frequently resolves to a delimiter, length, or bounds-checking defect - here the description explicitly characterises the outcome as an out-of-bounds write causing buffer corruption, behaviour that normally maps to the more specific CWE-787 (Out-of-Bounds Write). The practical consequence is that crafted or malformed input delivered to the CIPSAM interface is processed without adequate length or range validation, and the resulting write lands outside the intended buffer, corrupting adjacent data structures; because integrity and availability are both rated High while confidentiality is Low, the dominant risk is corruption or denial of the running service rather than bulk data disclosure. The changed-scope (S:C) metric reflects that the corruption can escape the vulnerable component's own security boundary and affect other parts of the NonStop environment, which is why an AV:L/PR:L flaw still reaches 8.7. CPE data identifies the affected product as hewlett_packard_enterprise:hpe_nonstop_cipsam with a wildcard version, meaning all builds up to and including T0693L02^BAU should be treated as vulnerable until the vendor fix is confirmed.

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

Description and vendor vector indicate local access (AV:L) by a privileged user (PR:L) triggering memory corruption with high integrity/availability impact; scope changed retained per CIPSAM crossing component boundaries.

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

Primary rating from Vendor (hpe).

CVSS VectorVendor: hpe

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

DescriptionCVE.org

A vulnerability in HPE NonStop CIPSAM allows an out-of-bounds write that can corrupt buffer data.

Executive ViewAI

Why It Matters

HPE NonStop CIPSAM versions T0693L02^BAU and earlier contain a high-severity memory corruption vulnerability (CVE-2026-76660) that allows an authenticated local user with low-level privileges to corrupt adjacent memory, potentially compromising data integrity and system availability. This affects organizations running mission-critical NonStop systems, where any disruption or data corruption can halt essential transaction processing and require costly recovery. Leadership should care because the platform often underpins core business operations, and the authenticated local attack vector reduces but does not eliminate risk from insider threats or compromised accounts.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting local access to trusted users only, enforcing least privilege to eliminate unnecessary low-level accounts, enabling file integrity monitoring and anomaly detection on NonStop systems, segmenting affected systems from other critical infrastructure, and maintaining offline backups to support rapid recovery if integrity or availability is compromised.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche mission-critical HPE NonStop platform, limited to specialized enterprise deployments
Social Media
2
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.1%
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
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

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

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