Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-73796 Overview
CVE-2026-73796 affects HPE NonStop TSQLEXE, the SQL execution component of the HPE NonStop platform. A locally authenticated user can submit a crafted SQL query that causes the application to crash. The flaw is categorized under CWE-564: SQL Injection: Hibernate, reflecting improper handling of SQL input that reaches the query processor. Exploitation requires low privileges and local access, with no user interaction. Impact is limited to integrity and availability of the targeted process, with no confidentiality exposure according to the published metrics.
Critical Impact
An authenticated local user can trigger an application crash in HPE NonStop TSQLEXE, disrupting SQL workloads running on the system.
Affected Products
- HPE NonStop TSQLEXE (specific affected versions listed in the HPE Security Bulletin)
Discovery Timeline
- 2026-10-14 - CVE CVE-2026-73796 published to NVD
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-73796
Vulnerability Analysis
The vulnerability resides in TSQLEXE, the SQL execution component of the HPE NonStop operating environment. When TSQLEXE parses or executes a specially crafted SQL query submitted by an authenticated local user, the process terminates abnormally. The result is a denial of service against the SQL execution path, affecting workloads that depend on that process. HPE classifies the issue under CWE-564, which addresses SQL input that is incorrectly processed by the underlying query engine.
Root Cause
The root cause is improper handling of a crafted SQL query by TSQLEXE. The component fails to safely process certain query structures, leading to an unhandled condition that crashes the running process. HPE has not published low-level technical details beyond the advisory. Administrators should consult the HPE Security Bulletin for the authoritative description and fixed versions.
Attack Vector
Exploitation requires local access to the NonStop system and a valid, low-privilege account capable of submitting SQL queries to TSQLEXE. No user interaction is required. An attacker who meets these preconditions can repeatedly trigger the crash to disrupt SQL processing. The vulnerability does not disclose data; impact is limited to integrity and availability of the affected process. No public proof-of-concept, exploit code, or evidence of in-the-wild exploitation has been reported at the time of publication.
No verified exploit code is available. Refer to the vendor advisory for technical details on the vulnerable query handling path.
Detection Methods for CVE-2026-73796
Indicators of Compromise
- Unexpected termination or restart events for the TSQLEXE process on HPE NonStop systems.
- SQL session errors or dropped connections correlated with specific user accounts submitting unusual query payloads.
- Repeated abnormal SQL parsing or execution errors in NonStop audit and operator logs.
Detection Strategies
- Monitor NonStop system event logs for TSQLEXE process aborts and automated restarts.
- Correlate SQL query submissions with process-crash timestamps to identify the originating session and account.
- Baseline normal query patterns per user and flag deviations such as malformed or structurally unusual SQL statements.
Monitoring Recommendations
- Forward NonStop operator and audit logs to a centralized analytics platform for correlation with authentication events.
- Alert on repeated TSQLEXE crashes originating from the same user, host, or application tier within short time windows.
- Review access to SQL execution interfaces and verify least-privilege assignments for interactive and batch SQL users.
How to Mitigate CVE-2026-73796
Immediate Actions Required
- Apply the fixed version of HPE NonStop TSQLEXE as specified in the HPE Security Bulletin.
- Inventory NonStop systems to identify instances running affected TSQLEXE versions.
- Restrict SQL execution privileges to users and service accounts with a documented operational need.
Patch Information
HPE has published a security bulletin addressing this issue. Fixed component versions and update instructions are available in the HPE Security Bulletin. Administrators should follow HPE's standard NonStop update procedures and validate the patched TSQLEXE version after deployment.
Workarounds
- Limit local account access to NonStop systems hosting TSQLEXE until the patch is applied.
- Review and remove unnecessary SQL execution privileges from interactive user accounts.
- Increase monitoring of TSQLEXE process stability and user query activity until remediation is complete.
# Configuration example
# Refer to the HPE Security Bulletin for authoritative upgrade and configuration guidance:
# https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbns05148en_us&docLocale=en_US
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

