Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach network-exposed NonStop SOAP endpoint
-
ExploitSend crafted SOAP request
-
ExecutionTrigger memory corruption in parser
-
ImpactCrash service, system down
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 network reachability to the HPE NonStop SOAP 4.0 web-services listener and the ability to submit a malicious SOAP request that the service parses; per CVSS PR:N/UI:N no authentication or user interaction is needed against a reachable endpoint. The principal limiting factor is exposure: NonStop SOAP services are typically deployed in restricted, internal mission-critical back-office environments (finance, telecom, retail switching) rather than on the public internet, so realistic risk depends heavily on whether the SOAP endpoint is network-accessible to the attacker. Impact is confined to a crash/system-down condition (A:H) with limited integrity effect (I:L) and no confidentiality exposure based on the vendor vector. |
| Impact | This is a moderate-priority availability issue rather than a top-tier emergency. The vendor CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:N/I:L/A:H, 8.2 HIGH) indicates a network-reachable, low-complexity, unauthenticated flaw whose dominant impact is availability (A:H, system down) with only limited integrity impact (I:L) and no confidentiality loss (C:N) - consistent with the description of memory corruption causing a crash rather than code execution. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no evidence of active or probable near-term exploitation; the high base score is driven by easy reachability and a denial-of-service outcome, not by demonstrated weaponization. One tension to verify: the input Tags label this a 'Buffer Overflow' and the description says 'memory corruption,' which often implies potential for code execution, yet both the CWE (CWE-20, improper input validation) and the C:N/I:L impact metrics point to a crash/DoS rather than RCE - if the vendor advisory indicates controllable corruption, the integrity/confidentiality impact could be understated. Overall, treat as a patch-soon availability risk for exposed NonStop SOAP endpoints, not a confirmed exploited threat. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a crafted SOAP request to an exposed HPE NonStop SOAP 4.0 service endpoint, triggering memory corruption in the request-parsing path. The malformed input crashes the service and brings the system down, causing a denial of service against the fault-tolerant NonStop environment. No public exploit code was identified at time of analysis, and the primary realistic outcome is service disruption rather than code execution. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Memory corruption in HPE NonStop SOAP 4.0 can be triggered remotely by a crafted SOAP request, resulting in a crash that takes down the affected NonStop system or SOAP service. The vulnerability is network-reachable and requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N), scoring 8.2 with the impact concentrated on availability (A:H) alongside a limited integrity effect (I:L) and no confidentiality exposure. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the realistic risk depends heavily on whether the SOAP listener is exposed beyond a restricted internal back-office network, making this a moderate-priority availability issue rather than a top-tier emergency.
RemediationAI
The authoritative fix information is HPE Security Bulletin hpesbns05148en_us (https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbns05148en_us&docLocale=en_US); an exact patched version or RVU is not confirmed in the available data, so consult that bulletin and apply the HPE-recommended NonStop SOAP 4.0 update or superseding release before relying on any workaround. Because the vector is PR:N/UI:N, authentication and user-interaction controls cannot mitigate this - any host that can reach the SOAP listener can attempt the attack - so the highest-value compensating control is network restriction: place the NonStop SOAP endpoint behind firewall or ACL rules that permit only the specific trusted integration hosts and management subnets, and confirm the listener is not reachable from the public internet or from broad corporate segments, accepting the trade-off that legitimate SOAP clients outside those ranges will lose connectivity and must be re-homed. Where the service must remain broadly reachable, front it with an XML/SOAP-aware inspection device or IPS/WAF that rejects malformed, oversized, or non-conforming SOAP envelopes and enforces schema validation, accepting the trade-off of false positives and possible latency or dropped legitimate payloads. Treat the service as availability-critical: enable monitoring and alerting on SOAP listener crashes, unexpected restarts, core dumps, and abnormal process termination as detection for exploitation attempts, and ensure NonStop failover/HA or restart automation is in place so that a successful crash does not translate into a sustained outage. No public exploit code was identified at time of analysis, but the low attack complexity means defenders should not rely on obscurity of the payload format.
Affected VersionsENISA
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
HPE NonStop SOAP 4.0 is a web-services component that exposes NonStop host functionality over SOAP/XML, meaning it parses attacker-influenced XML envelopes and method parameters on a network listener. The assigned weakness is CWE-20 (Improper Input Validation), which is the root-cause class covering the missing or insufficient validation of SOAP request content that permits malformed input to reach unsafe memory handling and cause corruption. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H describes a low-complexity, unauthenticated, network-based attack with no user interaction and an unchanged scope; the resulting impact is primarily a denial-of-service/system-down condition, with a small integrity component suggesting some corruption of data or state before failure but no leakage of information. The CPE cpe:2.3:a:hewlett_packard_enterprise:hpe_nonstop_soap_4.0:*:*:*:*:*:*:*:* indicates the issue is tracked against the 4.0 product line as a whole rather than a bounded version range, and vendor attribution comes from HPE's own security bulletin.
Know when Hpe Nonstop Soap 4 0 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:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Network-facing SOAP service parses attacker input with no auth or interaction (AV:N/AC:L/PR:N/UI:N); memory corruption yields system-down availability loss (A:H) with minor integrity impact and no confidentiality effect.
Primary rating from Vendor (hpe).
CVSS VectorVendor: hpe
DescriptionCVE.org
A security vulnerability in HPE NonStop SOAP 4.0 may cause memory corruption resulting in a system down.
Executive ViewAI
HPE NonStop SOAP 4.0 contains a remotely triggerable memory-corruption flaw that can crash the SOAP service or the underlying NonStop system, and it requires no authentication or user interaction to attempt (CVSS:3.1/AV:N/AC:L/PR:N/UI:N). Because NonStop platforms typically carry mission-critical transaction and payment workloads, the primary exposure is unplanned downtime rather than data loss, with no confidentiality impact and only limited integrity effect. Leadership should care if these SOAP listeners are reachable beyond tightly restricted back-office networks, since that determines whether this is a contained availability nuisance or a direct threat to a high-availability platform the business depends on.
No vendor-released patch identified at time of analysis. Interim mitigations: network segmentation and firewall/ACL restrictions limiting SOAP listener access to trusted back-office hosts only, disabling the SOAP service where not operationally required, fronting the listener with a request-validating reverse proxy or application-layer filter with rate limiting, and continuous SOAP service health monitoring with tested restart and failover procedures.
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
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.
EUVD-2026-101859
GHSA-p5qr-xr9q-hq5c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB