# CVE-2026-32747: SiYuan: Incomplete sensitive path blocklist in globalCopyFiles allows reading /proc and Docker secrets > An admin can bypass path restrictions to read sensitive files like /proc and Docker secrets, exposing credentials and environment variables. - **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Mar 2026 - **Updated:** 20 Mar 2026 - **Also known as:** GHSA-h5vh-m7fg-w5h6, GO-2026-4705 ## What is CVE-2026-32747? CVE-2026-32747 is a medium-severity path traversal vulnerability in B3log Siyuan, published on 19 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description SiYuan is a personal knowledge management system. In versions 3.6.0 and below, the globalCopyFiles API eads source files using filepath.Abs() with no workspace boundary check, relying solely on util.IsSensitivePath() whose blocklist omits /proc/, /run/secrets/, and home directory dotfiles. An admin can copy /proc/1/environ or Docker secrets into the workspace and read them via the standard file API. An admin can exfiltrate any file readable by the SiYuan process that falls outside the incomplete blocklist. In containerized deployments this includes all injected secrets and environment variables - a common pattern for passing credentials to containers. The exfiltrated files are then accessible via the standard workspace file API and persist until manually deleted. This issue has been fixed in version 3.6.1. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-184 (Incomplete List of Disallowed Inputs) ## Which versions are affected by CVE-2026-32747? 3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | None | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions to 0.0.0-20260313024916-fd6526133bb3 | None | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions to 0.0.0-20260313024916-fd6526133bb3 | None | Products: B3log Siyuan. ## How do I fix CVE-2026-32747? Upgrade to a fixed version. ## Is CVE-2026-32747 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32747 exists. ## Other vulnerabilities in B3log Siyuan - [CVE-2026-32938](https://insights.sbomify.com/CVE-2026-32938/): SiYuan has an Arbitrary File Read in its Desktop Publish Service (critical 9.9) - [CVE-2026-33669](https://insights.sbomify.com/CVE-2026-33669/): SiYuan has Arbitrary Document Reading within the Publishing Service (critical 9.8) - [CVE-2026-33670](https://insights.sbomify.com/CVE-2026-33670/): SiYuan has directory traversal within its publishing service (critical 9.8) - [CVE-2026-32767](https://insights.sbomify.com/CVE-2026-32767/): SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API (critical 9.8) - [CVE-2024-53504](https://insights.sbomify.com/CVE-2024-53504/): SQL injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32747 and fix it if it is affected. What it is: CVE-2026-32747 is a medium-severity path traversal vulnerability in B3log Siyuan, published on 19 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32747 exists. Affected packages and fixed versions: - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; no fix listed - github.com/siyuan-note/siyuan/kernel (Go): affected all versions up to 0.0.0-20260313024916-fd6526133bb3; no fix listed - github.com/siyuan-note/siyuan/kernel (Go): affected all versions up to 0.0.0-20260313024916-fd6526133bb3; no fix listed 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-32747/ (Markdown: https://insights.sbomify.com/CVE-2026-32747/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32747 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32747 - OSV: https://osv.dev/vulnerability/CVE-2026-32747 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32747/ Summaries are generated and may contain mistakes; the official description above is the record.