CVE-2026-79865 Unauthenticated Adjacent Memory Corruption Vulnerability leads to Remote Code Execution in AOS-10
Critical 9.6
Published
Updated
Check this codebase for CVE-2026-79865 and fix it if it is affected.
What it is: CVE-2026-79865 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-79865 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-79865/ (Markdown: https://insights.sbomify.com/CVE-2026-79865/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-79865?
CVE-2026-79865 is a critical vulnerability in Hewlett Packard Enterprise (HPE) ArubaOS (AOS), published on 22 Oct 2026.
Official description
A memory corruption vulnerability in the affected interface of AOS-10 could allow an unauthenticated adjacent attacker to achieve remote code execution. Successful exploitation could allow an attacker to execute arbitrary code as a privileged user on the underlying operating system.
Which versions are affected by CVE-2026-79865?
How do I fix CVE-2026-79865?
No fix has been published for CVE-2026-79865 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-79865 being exploited?
There is no known exploitation of CVE-2026-79865 in the wild and no public exploit code.
Sources
Also known as GHSA-rjqj-j4p2-v74r.