# CVE-2026-76742: Authentication Bypass in the Web Management Interface of AOS-S

> Unauthenticated remote attackers can bypass authentication in the HPE AOS-Switch web interface to gain unauthorized system access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 6 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-824j-mqpc-h7v9

## What is CVE-2026-76742?

CVE-2026-76742 is a critical authentication bypass vulnerability in Hewlett Packard Enterprise (HPE) AOS-Switch (AOS-S), published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication bypass vulnerabilities exist in the web management interface of AOS-S. Successful exploitation could allow an unauthenticated remote attacker to gain unauthorized access to the affected system.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-76742 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76742 is a critical authentication bypass vulnerability in Hewlett Packard Enterprise (HPE) AOS-Switch (AOS-S), published on 6 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-76742 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-76742/ (Markdown: https://insights.sbomify.com/CVE-2026-76742/index.md)
```

## Sources

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

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