Application crash via buffer overflow
Published Oct 15, 2026 · Updated Oct 15, 2026
A buffer overflow in HPE NonStop ODBC/MX Server allows attackers to crash the application through memory corruption via unspecified vectors. The available source description does not identify the affected function, input field, or incorrect buffer operation. Required privileges and the triggering input remain unspecified, and the documented consequence is an application crash rather than code execution.
Summary
What happened
A buffer overflow in HPE NonStop ODBC/MX Server allows attackers to crash the application through memory corruption via unspecified vectors. The available source description does not identify the affected function, input field, or incorrect buffer operation. Required privileges and the triggering input remain unspecified, and the documented consequence is an application crash rather than code execution.
The record
- CVE
- CVE-2026-79839
- Published
- Oct 15, 2026
- Updated
- Oct 15, 2026
- Vendor
- Hewlett Packard Enterprise
- Product
- HPE NonStop ODBC/MX Server
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 15, 2026CVE publishedPublication date reported by the CVE source.
- Oct 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=T7970L40 and earlier
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started