# CVE-2026-79890: Unauthenticated Command Injection Vulnerabilities in AOS-8 Accessed by the PAPI Protocol


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-78gw-mfhh-7cmf

## What is CVE-2026-79890?

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

### Official description

There are command injection vulnerabilities in AOS-8 that could lead to unauthenticated remote code execution by sending specially crafted PAPI packets. Successful exploitation of this vulnerability results in the ability to execute arbitrary code as a privileged user on the underlying operating system.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-79890 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79890 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-79890 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-79890/ (Markdown: https://insights.sbomify.com/CVE-2026-79890/index.md)
```

## Sources

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

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