# CVE-2026-95140: Path traversal in n/a

> Unauthenticated attackers can create arbitrary directories and write files outside the intended root via crafted requests in kkFileView.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-qj7c-283g-mmh2

## What is CVE-2026-95140?

CVE-2026-95140 is a high-severity path traversal vulnerability in n/a, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

kkFileView v5.0.0 through v5.0.2 contains a directory traversal vulnerability in FileController.java. The fileUpload, createFolder and existsFile endpoints accept a "path" parameter that is concatenated into the upload base path without validation, allowing unauthenticated attackers to create arbitrary directories and write arbitrary files outside the intended fileDir root via a crafted multipart request

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

## Which versions are affected by CVE-2026-95140?


## How do I fix CVE-2026-95140?

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

## Is CVE-2026-95140 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95140 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95140 and fix it if it is affected.

What it is: CVE-2026-95140 is a high-severity path traversal vulnerability in n/a, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95140 exists.

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-2026-95140/ (Markdown: https://insights.sbomify.com/CVE-2026-95140/index.md)
```

## Sources

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

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