# CVE-2025-37101: HPE OneView for VMware vCenter (OV4VC), Local Elevation of Privilege

> An attacker with read-only privileges can escalate to admin rights in HPE OneView for VMware vCenter, allowing unauthorized administrative actions.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-qf29-p5hq-gmj9

## What is CVE-2025-37101?

CVE-2025-37101 is a high-severity vulnerability in Hewlett Packard Enterprise HPE OneView for VMware vCenter, published on 26 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A potential security vulnerability has been identified in HPE OneView for VMware vCenter (OV4VC). This vulnerability could be exploited allowing an attacker with read only privilege to cause Vertical Privilege Escalation (operator can perform admin actions).

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2025-37101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-37101 is a high-severity vulnerability in Hewlett Packard Enterprise HPE OneView for VMware vCenter, published on 26 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-37101 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise HPE OneView for VMware vCenter. 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-37101/ (Markdown: https://insights.sbomify.com/CVE-2025-37101/index.md)
```

## Sources

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

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