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

> An attacker can execute arbitrary code by exploiting an untrusted search path vulnerability in NCP Secure Enterprise and Entry Windows Clients.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2025
- **Updated:** 2 Dec 2025
- **Also known as:** GHSA-4w6g-g6r5-3mgp

## What is CVE-2025-26155?

CVE-2025-26155 is a critical path traversal vulnerability in n/a, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NCP Secure Enterprise Client 13.18 and NCP Secure Entry Windows Client 13.19 have an Untrusted Search Path vulnerability.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 2 products.


Products: Ncp-E Ncp Secure Entry Client, Ncp-E Secure Enterprise Client.

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

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

## Is CVE-2025-26155 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17023](https://insights.sbomify.com/CVE-2017-17023/): Code injection in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26155 is a critical path traversal vulnerability in n/a, published on 26 Nov 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-26155 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-26155/ (Markdown: https://insights.sbomify.com/CVE-2025-26155/index.md)
```

## Sources

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

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