# CVE-2026-114376: leomoon-studios wiki-go API editor.go SourceHandler 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:** 28 Oct 2026
- **Also known as:** GHSA-8j56-2x2x-mr34, GHSA-wv68-7fq9-834c

## What is CVE-2026-114376?

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

### Official description

A weakness has been identified in leomoon-studios wiki-go up to 1.9.1. Affected by this vulnerability is the function SaveHandler/SourceHandler of the file internal/handlers/editor.go of the component API. Executing a manipulation can lead to path traversal. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 1.9.2 addresses this issue. This patch is called 94f7e73ef8df7c58091d72d77a5e26e9fdad98b8. Upgrading the affected component is advised.

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

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


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

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

## Is CVE-2026-114376 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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