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

confPath := filepath.Join(util.ConfDir, "conf.json")
if abs == confPath {
    return "", fmt.Errorf("access to conf.json is forbidden")
}

An MCP client with access to the file tool (post-fix for GHSA-cvhv-7xhj-xjp8, i.e. a properly
authenticated Administrator-level caller) can read data/.siyuan/publishAccess.json directly:

type PublishAccessItem struct {
    ID       string `json:"id"`
    Visible  bool   `json:"visible"`
    Password string `json:"password"` // plaintext; empty string = no password
    Disable  bool   `json:"disable"`
}

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."

data/templates and data/snippets/conf.json are lower-severity but still inconsistent with
the HTTP API's own precedent for what counts as sensitive.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-60083 has a CVSS score of 4.9 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20260808051406-3542530c505f); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Either replicate the full refuseToAccess() blocklist in resolvePath() (minimum fix, keeps
parity with the HTTP API going forward by extracting refuseToAccess's path list into a shared
helper both call), or implement the originally-recommended allowlist restricting the tool to
WorkspaceDir/temp/siyuan/*.log for read and disabling write/delete/rename/copy entirely unless
the caller is Administrator, matching the tool's own advertised "debugging/log reading only"
scope.

1. What is CVE-2026-60083? CVE-2026-60083 is a medium-severity incorrect authorization vulnerability in github.com/siyuan-note/siyuan/kernel (go), affecting versions < 0.0.0-20260808051406-3542530c505f. It is fixed in 0.0.0-20260808051406-3542530c505f. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-60083? CVE-2026-60083 has a CVSS score of 4.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/siyuan-note/siyuan/kernel are affected by CVE-2026-60083? github.com/siyuan-note/siyuan/kernel (go) versions < 0.0.0-20260808051406-3542530c505f is affected.
4. Is there a fix for CVE-2026-60083? Yes. CVE-2026-60083 is fixed in 0.0.0-20260808051406-3542530c505f. Upgrade to this version or later.
5. Is CVE-2026-60083 exploitable, and should I be worried? Whether CVE-2026-60083 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-60083 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-60083? Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260808051406-3542530c505f or later.

Other vulnerabilities in github.com/siyuan-note/siyuan/kernel