# CVE-2026-116168: SiYuan before v3.8.7 Path Traversal Local File Read via MCP Asset Tool


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 25 Oct 2026
- **Also known as:** GHSA-659w-8mpv-qcqc, GHSA-q768-4j87-gf3w

## What is CVE-2026-116168?

CVE-2026-116168 is a medium-severity vulnerability in siyuan-note siyuan, published on 25 Oct 2026. 

### Official description

SiYuan before 3.8.7 contains a path traversal vulnerability in the MCP asset tool because validateAssetUploadPaths relies on an incomplete sensitive-path blacklist that omits .env and other secret files. Authenticated attackers driving the MCP asset upload action can copy such local files into the workspace and read them back via /assets/ over HTTP.

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

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


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

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

## Is CVE-2026-116168 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116168 is a medium-severity vulnerability in siyuan-note siyuan, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116168 in the wild and no public exploit code.

Affected product: siyuan-note siyuan. 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-116168/ (Markdown: https://insights.sbomify.com/CVE-2026-116168/index.md)
```

## Sources

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

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