# CVE-2026-114377: leomoon-studios wiki-go Comment Deletion comments.go DeleteComment path traversal


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/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-fh2r-2crp-r75w, GHSA-g86r-58wp-4v86

## What is CVE-2026-114377?

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

### Official description

A security vulnerability has been detected in leomoon-studios wiki-go up to 1.9.1. Affected by this issue is the function DeleteComment of the file internal/comments/comments.go of the component Comment Deletion Handler. The manipulation of the argument documentPath leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 1.9.2 can resolve this issue. The identifier of the patch is 224ef2a11facddef6b3a3c1f0a69156d1e574a33. It is advisable to upgrade the affected component.

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

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


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

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

## Is CVE-2026-114377 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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