# CVE-2026-79850: Authentication Bypass Leading to Remote Code Execution in AOS-8


- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-3p2w-qx6f-5qxg

## What is CVE-2026-79850?

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

### Official description

Vulnerabilities in the affected interface of AOS-8 could allow an unauthenticated remote attacker to bypass existing authentication controls and run arbitrary commands on the underlying host. Successful exploitation could allow an attacker to execute arbitrary commands as root on the underlying operating system leading to complete system compromise.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-79850 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79850 is a critical vulnerability in Hewlett Packard Enterprise (HPE) ArubaOS (AOS), published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-79850 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-79850/ (Markdown: https://insights.sbomify.com/CVE-2026-79850/index.md)
```

## Sources

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

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