# CVE-2025-8054: Path Traversal vulnerability have been discovered in OpenText™ XM Fax.

> An attacker can exploit a path traversal flaw in OpenText XM Fax to arbitrarily disclose the content of files on the local filesystem.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/S:N/AU:Y/R:A/V:D/RE:M/U:Amber`)
- **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:** 19 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-5jm3-f2cq-hw7c

## What is CVE-2025-8054?

CVE-2025-8054 is a high-severity path traversal vulnerability in OpenText™ XM Fax, published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in OpenText™ XM Fax allows Path Traversal. 

The vulnerability could allow an attacker to arbitrarily disclose content of files on the local filesystem. This issue affects XM Fax: 24.2.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Opentext Xm Fax.

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

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

## Is CVE-2025-8054 being exploited?

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

## Other vulnerabilities in OpenText™ XM Fax

- [CVE-2025-8055](https://insights.sbomify.com/CVE-2025-8055/): SSRF vulnerability have been discovered in OpenText™ XM Fax (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8054 is a high-severity path traversal vulnerability in OpenText™ XM Fax, published on 19 Feb 2026. 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-8054 in the wild and no public exploit code.

Affected product: OpenText™ XM Fax. 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-8054/ (Markdown: https://insights.sbomify.com/CVE-2025-8054/index.md)
```

## Sources

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

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