# CVE-2025-14591: PII Leak Due to Change in EOR Handling

> Incorrect End-of-Record configuration in Delphix Continuous Compliance can cause PII to remain unmasked, leading to data exposure.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2025
- **Updated:** 22 Dec 2025
- **Also known as:** GHSA-mx97-2p44-ggx5

## What is CVE-2025-14591?

CVE-2025-14591 is a medium-severity vulnerability in Perforce Delphix Continuous Compliance, published on 20 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Delphix Continuous Compliance version 2025.3.0 and later, following a recent bug fix to correctly handle CR+LF (Windows and DOS) End-of-Record (EOR) characters in delimited files, an issue was identified: using an incorrect EOR configuration can cause inaccurate parsing and leave personally identifiable information (PII) unmasked.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Perforce Delphix Continuous Compliance.

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

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

## Is CVE-2025-14591 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14591 is a medium-severity vulnerability in Perforce Delphix Continuous Compliance, published on 20 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14591 in the wild and no public exploit code.

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

## Sources

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

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