ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-60083

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

Published Oct 27, 2026 · catalog updated Oct 27, 2026 · SiYuan: MCP file tool's

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-60083. EPSS is 0.39%. Act only if a listed version of SiYuan: MCP file tool's is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (SiYuan: MCP file tool's).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.39%
Remediation
Advisory link
Affected products
Go github.com/siyuan-note/siyuan/kernel · golang github.com

## Summary 's includes an explicit comment stating its sensitive-path blocklist is meant to align with the HTTP file API's established blacklist ( in ), following the remediation for GHSA-cvhv-7xhj-xjp8 ("Unauthenticated Administrator takeover exfiltrated via the MCP"), which specifically recommended restricting this tool's scope. In practice, the MCP tool implements only 1 of the 4 static blocklist entries the HTTP API enforces. ## Comparison blocks: 1. (API token, cookie signing key, accessAuthCode) 2. 3. the entire directory 4. 5. (dynamic, per-request) any path the current publish-mode session isn't authorized for blocks only: Items 2, 3, and 4 are absent. The tool's own / / / actions remain fully functional against them. ## Impact An MCP client with access to the tool (post-fix for GHSA-cvhv-7xhj-xjp8, i.e. a properly authenticated Administrator-level caller) can read directly: This exposes the plaintext access password for every publish-mode-shared notebook/document, letting the reader bypass password protection on any publish-mode share. This is a serious sibling issue given the volume of publish-mode access-control bugs already reported against this codebase — the passwords protecting exactly that feature are directly readable through a tool whose own description says "never use for workspace data." and are lower-severity but still inconsistent with the HTTP API's own precedent for what counts as sensitive. ## Why this is a distinct finding, not a duplicate GHSA-cvhv-7xhj-xjp8 was about *reachability* an unauthenticated Reader-tier JWT being forwarded to admin-scoped paths including . That has been fixed. This report is about the *tool's own scope* once reached by a legitimate, properly-authenticated caller, the remediation notes for that same advisory explicitly called for restricting to , which was not implemented; instead the tool retains workspace-wide scope with only a single-file blocklist addition. ## Suggested fix Either replicate the full blocklist

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/siyuan-note/siyuan/kernel0 → 0.0.0-20260808051406-3542530c505f
  • golang github.comversion unspecified

How to fix CVE-2026-60083

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-60083. EPSS is 0.39%. Act only if a listed version of SiYuan: MCP file tool's is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.0.0-20260808051406-3542530c505f. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-863: Incorrect Authorization. EPSS 0.39%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 27, 2026 · Go Vulnerability Database

    Detected

    ## Summary 's includes an explicit comment stating its sensitive-path blocklist is meant to align with the HTTP file API's established blacklist ( in ), following the remediation for GHSA-cvhv-7xhj-xjp8 ("Unauthenticated Administrator takeover exfiltrated via the MCP"), which specifically recommended restricting this tool's scope. In practice, the MCP tool implements only 1 of the 4 static blockli

  2. Oct 27, 2026 · Go Vulnerability Database

    Fix available

    github.com/siyuan-note/siyuan/kernel fixed in 0.0.0-20260808051406-3542530c505f

  3. Oct 27, 2026 · Go Vulnerability Database

    Fix available

    github.com/siyuan-note/siyuan/kernel fixed in 0.0.0-20260808051406-3542530c505f

  4. Oct 27, 2026 · Go Vulnerability Database

    Updated

    ## Summary 's includes an explicit comment stating its sensitive-path blocklist is meant to align with the HTTP file API's established blacklist ( in ), following the remediation for GHSA-cvhv-7xhj-xjp8 ("Unauthenticated Administrator takeover exfiltrated via the MCP"), which specifically recommended restricting this tool's scope. In practice, the MCP tool implements only 1 of the 4 static blockli

Sources

  • CVE.orgVulnerability recordCVE-2026-60083

    Official CVE identifier

    cve.org
  • GitLab Advisory DatabasePackage advisoryCVE-2026-60083

    kernel/mcp/tools/file.go's resolvePath() includes an explicit comment stating its sensitive-path blocklist is meant to align with the HTTP file API's established blacklist (refuseToAccess() in kernel/api/file.go), following the remediation for GHSA-cvhv-7xhj-xjp8 ("Unauthenticated Administrator takeover exfiltrated via the MCP"), which specifically recommended restricting this tool's scope. In pra

    advisories.gitlab.com
  • Go Vulnerability DatabasePackage advisoryGHSA-c8r8-95hg-mp34

    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

    osv.dev

References

Freshness

Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Go Vulnerability DatabaseOct 28, 2026
  • GitLab Advisory DatabaseOct 28, 2026
  • CVE.orgOct 27, 2026