# CVE-2026-79832: HPE NonStop SQL/MX Executor - Buffer overflow vulnerability

> A stack buffer overflow in HPE NonStop SQL/MX Executor allows attackers to disclose information or crash the process.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-fxm9-jr33-495j

## What is CVE-2026-79832?

CVE-2026-79832 is a high-severity memory corruption vulnerability in Hewlett Packard Enterprise HPE NonStop SQL/MX Executor, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A stack buffer overflow vulnerability in HPE NonStop SQL/MX Executor may potentially result in information disclosure or process crash.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-79832?


## How do I fix CVE-2026-79832?

No fix has been published for CVE-2026-79832 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-79832 being exploited?

There is no known exploitation of CVE-2026-79832 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-79832 and fix it if it is affected.

What it is: CVE-2026-79832 is a high-severity memory corruption vulnerability in Hewlett Packard Enterprise HPE NonStop SQL/MX Executor, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79832 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise HPE NonStop SQL/MX Executor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-79832/ (Markdown: https://insights.sbomify.com/CVE-2026-79832/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-79832
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-79832
- OSV: https://osv.dev/vulnerability/CVE-2026-79832

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-79832/
Summaries are generated and may contain mistakes; the official description above is the record.