Skip to main content

HPE NonStop ODBC/MX EUVDEUVD-2026-102091

| CVE-2026-79838 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-10-15 hpe GHSA-5j53-3mjc-qghx
7.3
CVSS 3.1 · Vendor: hpe
View

Attack ChainAIDerived

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

  1. Access
    Authenticate with low privileges on NonStop host
  2. Delivery
    Submit crafted input to ODBC/MX Services
  3. Exploit
    Overflow stack buffer (CWE-121)
  4. Execution
    Corrupt service memory
  5. Impact
    Crash service (denial of service)

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

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

Exploitation Conditions

Exploitation requires local access to the HPE NonStop system with at least low-level privileges (PR:L) AND user interaction (UI:R) - it is NOT remotely or unauthenticated-exploitable. The specific trigger is crafted input processed by HPE NonStop ODBC/MX Services that overflows a stack buffer (CWE-121). Limiting factors: the attacker must already have a valid local foothold with privileges, a user action is needed to deliver the malicious input, and the demonstrated impact per HPE is an application crash (availability), not confirmed arbitrary code execution. The affected component is specifically the ODBC/MX Services layer, so systems not using ODBC/MX connectivity are not exposed.

Impact

This is a moderate, not top-tier, priority. The provided CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:H, base 7.3) describes a LOCAL attack requiring existing low-level privileges AND user interaction, which substantially constrains real-world exploitability despite the 7.3 score - this is not a remotely reachable flaw. No EPSS score, KEV listing, 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 risk signals are therefore driven almost entirely by the CVSS vector and CWE-121 classification rather than observed threat activity. The impact is primarily denial of service: the description states only memory corruption 'resulting in application crash,' with high availability impact but no vendor claim of code execution - note the tension between the Scope:Changed / C:L / I:L metrics in the input and a description that mentions only a crash, suggesting the confidentiality/integrity sub-scores may be conservative speculation about memory corruption rather than demonstrated outcomes; verify with HPE. Because HPE NonStop is a niche fault-tolerant platform, both the attack surface (local, authenticated) and the deployment footprint keep practical risk well below what the raw score implies.

Exploit ScenarioDerived

A local user with low-level privileges on an HPE NonStop system interacts with ODBC/MX Services (e.g., supplies a crafted input through a client operation requiring user action) that overflows a stack buffer, corrupting memory and crashing the service. No public exploit code is available, and the realistic outcome per the vendor description is a denial-of-service crash rather than confirmed code execution. Exploitation is bounded by the need for pre-existing local access and user interaction.

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

HPE NonStop ODBC/MX Services contains a stack-based buffer overflow (CWE-121) that allows a locally authenticated attacker with low privileges to crash the application via crafted input, provided a user action is performed. The vulnerability is not remotely exploitable and requires user interaction; no public exploit was identified at time of analysis. Per independent assessment, the impact is limited to availability (application crash), with no confirmed confidentiality or integrity impact.

RemediationAI

Apply the patches or upgrades specified in the HPE advisory (hpessbns05148en_us) to remediate this buffer overflow. No explicit fixed version is provided in the available data; consult the advisory for exact version information. As a compensating control, limit local login privileges to only trusted users, and disable or restrict the ODBC/MX Services component if it is not required for business operations-though disabling ODBC/MX may break database connectivity for dependent applications. Because exploitation requires user interaction, avoid processing untrusted input through the service and ensure that users are aware of the risks of opening untrusted files or data. No public exploit was identified at time of analysis, so prioritize patching based on your risk profile.

Affected VersionsENISA

HPE NonStop ODBC/MX Services T7969L40 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 vulnerability is a stack-based buffer overflow (CWE-121) in the HPE NonStop ODBC/MX Services component, which provides ODBC and MX connectivity for HPE NonStop systems. A crafted input, when processed by the service, overflows a fixed-size stack buffer, causing memory corruption that can lead to an application crash. The affected product is identified by CPE cpe:2.3:a:hewlett_packard_enterprise:hpe_nonstop_odbc/mx_services:*:*:*:*:*:*:*:*, indicating that all versions of the service are potentially vulnerable unless patched. The independent CVSS assessment (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H) confirms that exploitation requires local access, low privileges, and user interaction, with only availability impact. The original NVD vector included scope change and low confidentiality/integrity impacts, but the assessed vector reflects HPE's description of a crash-only impact. The affected component is the ODBC/MX Services layer, so systems not using ODBC/MX connectivity are not exposed.

Know when Hpe Nonstop Odbc Mx Services 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.3 HIGH
AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:H
vuln.today AI 5.0 MEDIUM

Local authenticated access with required user interaction yields AV:L/PR:L/UI:R; the description states only a crash, so A:H with C/I:N and no demonstrated cross-component impact (S:U).

3.1 AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
High

DescriptionCVE.org

A buffer overflow vulnerability in HPE NonStop ODBC/MX Services may cause memory corruption, resulting in application crash.

Executive ViewAI

Why It Matters

HPE NonStop ODBC/MX Services contains a high-severity stack buffer overflow that can cause application crashes when triggered by a local user, potentially disrupting critical transaction processing. Although exploitation requires local access and user interaction, the absence of a vendor patch leaves organizations exposed to availability impacts. Leadership should ensure interim mitigations are in place and monitor for a future patch.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Restrict local access to HPE NonStop ODBC/MX Services, enforce least privilege, monitor for application crashes, and conduct user awareness on untrusted input.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
HPE NonStop is niche fault-tolerant hardware used mainly in finance/telecom
Data Quality
3 sources
Confidence: Low

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
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
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.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

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