# CVE-2026-79833: HPE NonStop ANSI SQLUTIL - Denial of Service vulnerability

> A remote unauthenticated attacker can cause the HPE NonStop ANSI SQLUTIL service to terminate unexpectedly, resulting in a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-xpvr-q7rw-ww5m

## What is CVE-2026-79833?

CVE-2026-79833 is a high-severity denial of service vulnerability in Hewlett Packard Enterprise HPE NonStop ANSI SQLUTIL, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in HPE NonStop ANSI SQLUTIL may allow a remote unauthenticated actor to cause an affected service to terminate unexpectedly, causing a denial of service.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2026-79833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79833 is a high-severity denial of service vulnerability in Hewlett Packard Enterprise HPE NonStop ANSI SQLUTIL, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79833 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise HPE NonStop ANSI SQLUTIL. 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-79833/ (Markdown: https://insights.sbomify.com/CVE-2026-79833/index.md)
```

## Sources

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

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