# CVE-2026-114375: leomoon-studios wiki-go Files Rename API files.go RenameFileHandler path traversal


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-g2j6-cvc8-3ff3, GHSA-xg75-vx57-m5mx

## What is CVE-2026-114375?

CVE-2026-114375 is a medium-severity vulnerability in leomoon-studios wiki-go, published on 21 Oct 2026. 

### Official description

A security flaw has been discovered in leomoon-studios wiki-go up to 1.9.1. Affected is the function RenameFileHandler of the file internal/handlers/files.go of the component Files Rename API. Performing a manipulation of the argument currentPath/newName results in path traversal. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 1.9.2 is able to address this issue. The patch is named 81cd12e248314a52605f0f39718c8a76272eac29. It is recommended to upgrade the affected component.

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

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


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

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

## Is CVE-2026-114375 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114375 is a medium-severity vulnerability in leomoon-studios wiki-go, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114375 exists.

Affected product: leomoon-studios wiki-go. 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-114375/ (Markdown: https://insights.sbomify.com/CVE-2026-114375/index.md)
```

## Sources

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

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