# CVE-2026-126776: SiYuan 3.7.0 before 3.8.10 Path Traversal File Write via MCP web_fetch

> Attackers controlling URLs fetched by SiYuan's MCP tools can write files outside the import directory on Windows.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-fgx6-mcm3-mrhr, GHSA-hq2c-hh95-vrr6

## What is CVE-2026-126776?

CVE-2026-126776 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SiYuan 3.7.0 before 3.8.10 on Windows contains a path traversal vulnerability in kernel/util/webfetch.go that allows attackers to write files outside the import directory via backslash-encoded filenames. Attackers controlling a URL fetched by the MCP web_fetch or http_request tools can use %5C-encoded ..\ sequences to write chosen response bytes to directories above temp/import that are writable by the SiYuan user.

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

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-126776 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126776 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-126776 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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