# CVE-2025-2903: Privilege Chaining in Delphix

> Attackers can gain SSH command-line control and escalate privileges on Delphix VMs deployed on GCP with OS Login enabled.

- **Severity:** High 8.5 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H`)
- **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:** 17 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-gq47-h9vq-4rp9

## What is CVE-2025-2903?

CVE-2025-2903 is a high-severity vulnerability in Perforce Delphix, published on 17 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An attacker with knowledge of creating user accounts during VM deployment on Google Cloud Platform (GCP) using the OS Login feature, can login via SSH gaining command-line control of the operating system. This allows an attacker to gain access to sensitive data stored on the VM, install malicious software, and disrupt or disable the functionality of the VM.

Weakness: CWE-268 (Privilege Chaining), CWE-267 (Privilege Defined With Unsafe Actions)

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


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

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

## Is CVE-2025-2903 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2903 is a high-severity vulnerability in Perforce Delphix, published on 17 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-2903 in the wild and no public exploit code.

Affected product: Perforce Delphix. 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-2903/ (Markdown: https://insights.sbomify.com/CVE-2025-2903/index.md)
```

## Sources

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

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