# CVE-2025-48026: Path traversal in n/a

> An unauthenticated attacker can exploit a path traversal vulnerability in Mitel OpenScape Xpressions to read sensitive files from the underlying operating system.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-f8xm-pm69-gjcp

## What is CVE-2025-48026?

CVE-2025-48026 is a high-severity path traversal vulnerability in n/a, published on 23 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the WebApl component of Mitel OpenScape Xpressions through V7R1 FR5 HF43 P913 could allow an unauthenticated attacker to conduct a path traversal attack due to insufficient input validation. A successful exploit could allow an attacker to read files from the underlying OS and obtain sensitive information.

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

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


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

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

## Is CVE-2025-48026 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48026 is a high-severity path traversal vulnerability in n/a, published on 23 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48026 in the wild and no public exploit code.

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

## Sources

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

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