# CVE-2025-27080: Authenticated Sensitive Information Disclosure exposes Credentials in AOS-CX Command Line Interface

> Authenticated attackers can expose sensitive credentials via the CLI, enabling unauthorized access to external services and lateral movement.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2025
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-q494-jhv5-r89f

## What is CVE-2025-27080?

CVE-2025-27080 is a medium-severity vulnerability in Hewlett Packard Enterprise (HPE) AOS-CX, published on 18 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerabilities in the command line interface of AOS-CX could allow an authenticated remote attacker to expose sensitive information. Successful exploitation could allow an attacker to gain unauthorized access to services outside of the impacted switch, potentially leading to lateral movement involving those services.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-27080 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27080 is a medium-severity vulnerability in Hewlett Packard Enterprise (HPE) AOS-CX, published on 18 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27080 in the wild and no public exploit code.

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

## Sources

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

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