CVE-2026-95721 Authenticated Local Memory Corruption Vulnerability in AOS-8 Web-Based Management Interface
Low 3.3
Published
Updated
Check this codebase for CVE-2026-95721 and fix it if it is affected.
What it is: CVE-2026-95721 is a low-severity vulnerability in Hewlett Packard Enterprise (HPE) ArubaOS (AOS), published on 22 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-95721 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-95721/ (Markdown: https://insights.sbomify.com/CVE-2026-95721/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-95721?
CVE-2026-95721 is a low-severity vulnerability in Hewlett Packard Enterprise (HPE) ArubaOS (AOS), published on 22 Oct 2026.
Official description
A memory corruption vulnerability exists in the web-based management interface of AOS-8. Successful exploitation could allow an authenticated low privilege attacker with local access to view some system files and interrupt the normal operation of the affected service.
Weakness: CWE-119
Which versions are affected by CVE-2026-95721?
How do I fix CVE-2026-95721?
No fix has been published for CVE-2026-95721 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-95721 being exploited?
There is no known exploitation of CVE-2026-95721 in the wild and no public exploit code.
Sources
Also known as GHSA-4fwx-xpj5-8c4f.