# CVE-2026-95713: Unauthenticated Buffer Overflow Vulnerability leads to Denial-of-Service in AOS-8 Command Line Interface


- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-crvf-mq9h-4gf3

## What is CVE-2026-95713?

CVE-2026-95713 is a high-severity vulnerability in Hewlett Packard Enterprise (HPE) ArubaOS (AOS), published on 22 Oct 2026. 

### Official description

An unauthenticated buffer overflow vulnerability exists in the command line interface of AOS-8. Successful exploitation could allow an unauthenticated remote attacker to disrupt the availability of the affected interface, along with limited access to or modification of some system data.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-95713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95713 is a high-severity vulnerability in Hewlett Packard Enterprise (HPE) ArubaOS (AOS), published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-95713 in the wild and no public exploit code.

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

## Sources

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

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