# CVE-2025-27078: Authenticated Remote Command Execution caused by Insecure Function Usage in System Binary

> Authenticated attackers can inject OS commands via the CLI in HPE AOS Access Points, leading to complete system compromise.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-8vjw-ghh4-xxg8

## What is CVE-2025-27078?

CVE-2025-27078 is a medium-severity command injection vulnerability in Hewlett Packard Enterprise (HPE) AOS-10 AP, published on 8 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in a system binary of AOS-8 Instant and AOS-10 AP could allow an authenticated remote attacker to inject commands into the underlying operating system while using the CLI. Successful exploitation could lead to complete system compromise.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-27078?


## How do I fix CVE-2025-27078?

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

## Is CVE-2025-27078 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27078 and fix it if it is affected.

What it is: CVE-2025-27078 is a medium-severity command injection vulnerability in Hewlett Packard Enterprise (HPE) AOS-10 AP, published on 8 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27078 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) AOS-10 AP. 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-2025-27078/ (Markdown: https://insights.sbomify.com/CVE-2025-27078/index.md)
```

## Sources

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

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