# SiYuan: MCP file tool's blocklist is incomplete relative to the HTTP file API it claims to align with, exposing publish-mode passwords and other sensitive workspace files

Advisory record · `GHSA-c8r8-95hg-mp34`

- **Identifiers:** `GHSA-c8r8-95hg-mp34` · `CVE-2026-60083` · `GO-2026-6863`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 27 Oct 2026
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Oct 2026, 14:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/siyuan-note/siyuan/kernel` (Go): affected `<0.0.0-20260808051406-3542530c505f`; fixed in `0.0.0-20260808051406-3542530c505f`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Record GHSA-c8r8-95hg-mp34 concerns the SiYuan kernel Go package, affected at versions before 0.0.0-20260808051406-3542530c505f and fixed in that version. The MCP file tool's sensitive-path blocklist covers only one of the four entries enforced by the HTTP file API, so an authenticated administrator-level MCP client can read files such as data/.siyuan/publishAccess.json, which holds publish-mode access passwords. Upgrade to 0.0.0-20260808051406-3542530c505f or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.9 Medium, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 33rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c8r8-95hg-mp34)

## Sources

- [GitHub Advisory Database: GHSA-c8r8-95hg-mp34](https://github.com/advisories/GHSA-c8r8-95hg-mp34)
- [OSV: GHSA-c8r8-95hg-mp34](https://osv.dev/vulnerability/GHSA-c8r8-95hg-mp34)
- <https://github.com/siyuan-note/siyuan/security/advisories/GHSA-c8r8-95hg-mp34>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-60083>
- <https://github.com/siyuan-note/siyuan/commit/3542530c505f13aa3fbd0343627409ca6c000dd2>
- <https://github.com/siyuan-note/siyuan>
- <https://github.com/siyuan-note/siyuan/releases/tag/v3.8.0>
- <https://www.vulncheck.com/advisories/siyuan-before-incomplete-path-blocklist-via-mcp-file-tool>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c8r8-95hg-mp34>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c8r8-95hg-mp34/>. Everything for agents: <https://agentprime.io/llms.txt>.