# CVE-2026-60083: SiYuan before v3.8.0 Incomplete Path Blocklist via MCP file tool

> Authenticated administrators can bypass path restrictions to read sensitive files like plaintext passwords and configuration data.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-c8r8-95hg-mp34

## What is CVE-2026-60083?

CVE-2026-60083 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 22 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SiYuan versions before v3.8.0 contain an incomplete path blocklist in the MCP file tool that fails to restrict access to sensitive workspace files protected by the HTTP API. Authenticated administrators can read plaintext publish-mode passwords from data/.siyuan/publishAccess.json and access other sensitive files like data/templates and data/snippets/conf.json.

Weakness: CWE-863 (Incorrect Authorization)

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

2 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260808051406-3542530c505f |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260808051406-3542530c505f |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260808051406-3542530c505f or later.

## Is CVE-2026-60083 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60083 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 22 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60083 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260808051406-3542530c505f
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260808051406-3542530c505f

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

## Sources

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

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