# CVE-2025-37088: Race condition in HPE Cray Data Virtualization Service (DVS)

> A race condition in HPE Cray DVS allows local or cluster users to gain unauthorized access under specific configurations.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2025
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-qch9-x3vr-h45w

## What is CVE-2025-37088?

CVE-2025-37088 is a medium-severity vulnerability in Hewlett Packard Enterprise (HPE) HPE Cray Data Virtualization Service (DVS), published on 22 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability has been identified in HPE Cray Data Virtualization Service (DVS). Depending on race conditions and configuration, this vulnerability may lead to local/cluster unauthorized access.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

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

## Is CVE-2025-37088 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-37088 is a medium-severity vulnerability in Hewlett Packard Enterprise (HPE) HPE Cray Data Virtualization Service (DVS), published on 22 Apr 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-37088 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) HPE Cray Data Virtualization Service (DVS). 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-37088/ (Markdown: https://insights.sbomify.com/CVE-2025-37088/index.md)
```

## Sources

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

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