# CVE-2026-76741: Authenticated Buffer Overflow Vulnerabilities lead to Denial-of-Service in AOS-S

> An authenticated remote attacker can trigger a buffer overflow in HPE AOS-Switch to cause a denial-of-service condition.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-8j79-v8wq-px92

## What is CVE-2026-76741?

CVE-2026-76741 is a medium-severity memory corruption vulnerability in Hewlett Packard Enterprise (HPE) AOS-Switch (AOS-S), published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow vulnerabilities exist in the affected interface of AOS-S. Successful exploitation could allow an authenticated remote attacker to cause a denial-of-service condition on the affected system.

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

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


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

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

## Is CVE-2026-76741 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76741 is a medium-severity memory corruption vulnerability in Hewlett Packard Enterprise (HPE) AOS-Switch (AOS-S), published on 6 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-76741 in the wild and no public exploit code.

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

## Sources

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

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